If you working with Node.js you probably interact with the database (MongoDB, PostgreSQL, and etc) via ORM.
But sometimes typical ORM does not co...
For further actions, you may consider blocking this person and/or reporting abuse
IMHO, knex and typescript don't go together, prisma has much better typescript support and they have good solutions for nested queries, inclusions and selections, you should check it out!
Prisma looks quite awesome but knex has three features we need in our software which I could not do with Prisma.
Those features are running rock solid with knex, in combination with Objection I have a good typescript support. Knex might look not as fancy as Prisma and feels more old fashioned, but I would not switch to Prisma in their current stage of development
Of course knex is not garbage, and it's been one of the most used query builders for ages, but in my company we are making the transition from knex to prisma because as i said in another comment, the advantages are greater than the drawbacks
Never worked with Prisma.
But i see one problems:
And the points because of which I do not consider Knex a bad choice:
Repository pattern not a panacea, it all depends on your tasks 😉
The first argument is bad just because it is not a good choice to use webdev tools to do data engineer stuff, if you need big data manipulations in the samedatabase that you use to keep ordinary webapp data, something is structurally wrong
That's a more than good argument, if we're talking about the same thing (the SQL-only migrations). In ideal world that wouldn't happen, but in real world I definitely came into scenario where yes, something was wrong with the database schema, but if you get to that point, having Prisma with its current toolset will screw you over and try then explaining that to the client. Having some other ORM with programatic migrations solves a huge pain point there because you are able to run any logical operations you wish over the database.
I am also not sure I completely follow your point though. Database migrations should definitely be handled by a single tool which ORM's are usually for.
We are currently looking for a US developer. It would be ideal if we utilized your account to handle financial matters, including account growth and bidding, while you handled the development. It would take 2-3 years to raise your account to a Job Success, top-rated level on your own, but thanks to our extensive network of clients, we can improve your account in just two months. We will pay you 15%-20% of the profits. If u have any question, DM me please. thanks
I don’t get the fact that you use an async executor while you instantiate a new Promise
Indeed, fixed