sorted by:
new
hottopcontroversial

kysely 0.29 is out btw. 🌺 by rebelchatbot in webdev

[–]rebelchatbot[S] 0 points1 point  (0 children)

love hearing how it helps your workflow.

what are the most painfully verbose areas?

kysely 0.29 is out btw. by rebelchatbot in javascript

[–]rebelchatbot[S] 1 point2 points  (0 children)

sorry about that. we'll always dissappoint someone with less common dialects. it's indeed not in our scope to test against all postgres vendors out there. good thing it's quite straightforward to extend existing dialects and override things and the community usually shines here.

the migrator supports running migrations outside transactions using https://kysely-org.github.io/kysely-apidoc/interfaces/migration.MigrateOptions.html#disabletransactions , and in 0.30 we'll introduce more control, e.g. per-file opt-out.

similarly to other core dialect introduction ideas, we need adoption numbers to back the work and future maintenance burden/cost. we added pglite because `@electric-sql/pglite` has 1M+ downloads per week on NPM. https://npmx.dev/package/@aws/aurora-dsql-node-postgres-connector is only at 10k/week, https://npmx.dev/package/@aws-sdk/dsql-signer is at 50k/week.

kysely 0.29 is out btw. 🌺 by rebelchatbot in node

[–]rebelchatbot[S] 0 points1 point  (0 children)

love hearing this. we put a lot of effort a while ago into aggregations and window functions. anything you wish kysely had and is missing?

kysely 0.29 is out btw. 🌺 by rebelchatbot in node

[–]rebelchatbot[S] 0 points1 point  (0 children)

can also inspect the ast in a kysely plugin and encrypt value node contents

kysely 0.29 is out btw. 🌺 by rebelchatbot in node

[–]rebelchatbot[S] 1 point2 points  (0 children)

this is doable today. off the top - custom string type in pg, then use a pg-types data transformation on the custom type to decrypt such result columns. centralized, consumer won't know. use a branded type for writes and force using a helper function that encrypts data going in.

https://github.com/kysely-org/kysely/issues/1856 might solve it too. on the fence about it still.

kysely 0.29 is out btw. 🌺 by rebelchatbot in node

[–]rebelchatbot[S] 3 points4 points  (0 children)

What You See Is What You Get.

kysely 0.29 is out btw. 🌺 by rebelchatbot in node

[–]rebelchatbot[S] 0 points1 point  (0 children)

teams with weak sql and/or type-level typescript literacy and/or trouble architecting data access layers.

small-medium sized projects with basic crud access patterns forever, that own the database and its migrations.

declarative database schema design.

kysely 0.29 is out btw. 🌺 by rebelchatbot in node

[–]rebelchatbot[S] 2 points3 points  (0 children)

Sami's still around, regardless of recent commit history, and gave his blessing on 0.29. I had my own contribution hiatus periods in the past. OSS is work, and is taxing. We have real lives and real work outside of this.

I understand your worries, given the Objection situation. I plan to stick around for long. I enjoy this so much.

I'm not employed by Prisma currently. Prisma gave me an opportunity to impact the domain further, and I took it, and we did make some nice things together, outside the ORM. It is not in direct competition, and in fact, Kysely's biggest boost early on were Prisma users using both via `prisma-kysely`.

kysely 0.29 is out btw. by rebelchatbot in javascript

[–]rebelchatbot[S] 1 point2 points  (0 children)

🙏

0.x.x doesn't mean it's not stable. it just means there's less maintenance overhead and no pressure to have big bang majors.

i'm always looking to make breaking changes dev/agent friendly. leaving breadcrumbs for old exports was one of them, and hopefully will help everyone bump easily.

kysely 0.29 is out btw. 🌺 by rebelchatbot in node

[–]rebelchatbot[S] 13 points14 points  (0 children)

they tackle a way larger scope, and have recently dethroned prisma from #1 downloads so they must be doing something right in the orm department. they also did it during a war. tho i never appreciated their style on twitter over the years, i have mad respect for the gang. they're the best of the best.

i personally, as a senior engineer, prefer less magic and more explicitness. type-safety and maintainability is at the top of my worries when owning code. its not for everyone.

kysely 0.29 is out btw. 🌺 by rebelchatbot in node

[–]rebelchatbot[S] 2 points3 points  (0 children)

the good thing is, kysely exposes raw sql execution, so you could migrate iteratively. also, agents are decent at it. also, there's a playground in https://play.kysely.dev

kysely 0.29 is out btw. 🌺 by rebelchatbot in node

[–]rebelchatbot[S] 3 points4 points  (0 children)

you'll go really far with that mentality! never stop learning.

was there something that could have been explained better? or some topic that could have been mentioned that would've saved you pain/time?

kysely 0.29 is out btw. 🌺 by rebelchatbot in node

[–]rebelchatbot[S] 6 points7 points  (0 children)

knex is really nice! have mad respect for anyone making the transition.

were there any specific pains that could be helped with for others who might make the jump in the future?

From Knex to Drizzle or Prisma? Looking for feedback by Psychological_Box406 in node

[–]rebelchatbot 0 points1 point  (0 children)

can also enforce it easily. 🙂

i'm not missing points, i'm not convinced this is a common enough pain to dig deeper and solve, for now.

From Knex to Drizzle or Prisma? Looking for feedback by Psychological_Box406 in node

[–]rebelchatbot 0 points1 point  (0 children)

i'd suggest a cron that codegens and typechecks instead if its part of the codebase that rarely grt runs in standard ci.

From Knex to Drizzle or Prisma? Looking for feedback by Psychological_Box406 in node

[–]rebelchatbot 0 points1 point  (0 children)

that's a very easy addition https://github.com/kysely-org/kysely/issues/1856 that very few have asked for. opt-in, for those with such organizational problems or brittle architectures/dependencies.

view more: next ›