Live data from Hacker News

Viewing profile — igalklebanov

igalklebanov

HN member
Joined
Sat, May 20, 2023, 11:50 AM UTC
HN karma
15
Public activity
29 items

About igalklebanov

kysely co-lead, zod contributor.

Recent public activity

  1. comment
    Comment #48249815

    here's a good write up on the type-safety advantages https://github.com/thetutlage/meta/discussions/8

  2. comment
    Comment #48249804

    As far as query building goes, `kysely` is more in-depth, type-safe, expressive, 1:1 and doesn't require importing as many things. `kysely-ctl` doesn't generate migrations for you,…

  3. comment
    Comment #48248240

    Hey DISCLAIMER: I'm co-leading the org/project. We recently broke 6M downloads per week on NPM, and became 3rd after `drizzle-orm` and `@prisma/client`. If you haven't tried it yet…

  4. story
  5. comment
    Comment #43675789

    can you share your personal documentation story? what did you not find? what was painful?

  6. comment
    Comment #43675770

    it depends on the database. the major ones support savepoints. postgres included. https://www.postgresql.org/docs/current/sql-savepoint.html https://dev.mysql.com/doc/refman/8.4/en…

  7. comment
    Comment #43675334

    thoughts? requests? issues? <3

  8. story
  9. comment
    Comment #36428700

    JOOQ is cool! What do you mean by "better type safety"? Kysely's ecosystem has 2 codegen libraries: kysely-codegen introspects the database directly. prisma-kysely generates types …

  10. comment
    Comment #36428602

    Looks cool! Kysely was inspired by Knex, but took a more predictable route instead of providing generic APIs that produce different SQL for different dialects. We believe that dial…

  11. comment
    Comment #36428578

    postgres.js is dope! I'm maintaining a Kysely community dialect for it. https://github.com/igalklebanov/kysely-postgres-js

  12. comment
    Comment #36428573

    Would love to have a discussion about your use case in our discord. We're constantly thinking about improving that part of our API as it's at the heart of many things.

  13. comment
    Comment #36423456

    Huge shoutout to our community, bloggers and youtubers! https://github.com/kysely-org/awesome-kysely

  14. comment
    Comment #36423288

    <3 from Kysely. kysely-codegen is dope!

  15. comment
    Comment #36422915

    I'd suggest you try them both, and pick what you like better or what feels safer to bet on for your project. I know some of our users use both, zapatos for codegen and kysely for q…

  16. comment
    Comment #36422656

    It was also requested in prisma-kysely recently. Might be a good idea to check kysely-codegen's issues section and open an issue if it wasn't requested yet.

  17. comment
    Comment #36422608

    Hey :wave: Igal from Kysely here (I did not create it, Sami did). Our site is a constant WIP. We've recently revamped "Getting Started" and added a lot of examples. If you can't fi…

  18. comment
    Comment #36422316

    We love Knex, and are inspired by it. Sadly its not type-safe and reaching type-safety would require a rewrite. We care a lot about our TypeScript compilation performance and Devel…

  19. comment
    Comment #36422233

    Kysely has community projects that offer Database interface auto-generation. kysely-codegen can introspect all core dialects. prisma-kysely can generate straight from Prisma schema…

  20. comment
    Comment #36422165

    > which supports automatic type-safety for complex joins, CTEs, subselects etc. I evaluated Kysely as well but found the sql feature set coverage of ts-sql-query better at the time…

  21. comment
    Comment #36421285

    <3 from Kysely. kysely-codegen is really dope!

  22. comment
    Comment #36421267

    <3 from Kysely. prisma-kysely is dope!

  23. comment
    Comment #36421254

    <3 from Kysely.

  24. comment
    Comment #36421240

    Have you read this recipe? https://kysely.dev/docs/recipes/relations

  25. comment
    Comment #36421212

    Kysely is not an ORM, its a query builder with strong emphasis on type-safety and 1:1* mapping ("What You See Is What You Get") to SQL. Projects writing raw SQL eventually end up i…