kysely

Honestly any typescript library with great type safety probably has seriously gnarly generics inside. Here[1] is a random file from kysely, which is surprisingly readable even though kysely's type safety is incredibly good. But things I encounter in the regular non-library world are usually recursive types that have specific constraints. A couple years ago I had my first foray into typescript generics, and was so stumped that I actually gave up. I was trying to map the type of one nested object to another. This[2] is the stackoverflow post from the legendary jcalz that saved me! Check jcalz's link to the TS playground [1]https://github.com/kysely-org/kysely/blob/master/src/query-b... [2]https://stackoverflow.com/questions/72461962/is-it-possible-...

This was one of the problems I ran into https://github.com/kysely-org/kysely/issues/664, not being able to use functions inside onDuplicateKeyUpdate

The most interesting JS DB lib I came across was https://github.com/kysely-org/kysely but still didn't feel as good as EF Core.

Hello HN! I was recently introduced to Kysely (https://github.com/kysely-org/kysely), a type-safe Typescript SQL query builder, and instantly fell in love! I got inspired and wanted to make something similar for AWS DynamoDB. Thus, I developed Tsynamo! Instead of calling it type-safe, I decided to go with type-friendly, because the library is still in an early stage, and is not 100% type-safe. Under the hood, Tsynamo compiles the built queries into AWS SDK v3 commands. I feel that Tsynamo simplifies the AWS SDK API quite a lot since the developer doesn't have to mess around with condition/filter expressions or attribute names/values themselves, and as a bonus gets autocompletion for building the queries! There's also a playground to test it out in your browser: https://try.tsynamo.dev. It might not have the most up-to-date API of the lib

Started going really deep into SQLite. Couple hiccups like making sure when creating tables to use strict mode and enabling foreign keys that every one needs to read about. I exported about 8million rows from my Apple health records (about eight years for something’s like steps from before watch) and into a SQLite database from the xml dump using python (twice as fast a rust for some reason) in about 110 seconds. Dates are stored as Unix time stamps. Had ChatGPT generate some queries that showed my percent change in things like resting heart rate for each year using LAG and AVG return in less than a second. My job at work https://unsupervised.com/ does a lot of KPI work so I’ve been interesting in learning how to to correlate data to show improvements to KPIs (in my case resting heart rate or lean body mass) Nextjs server components and

You can use D1 with Kysely (the typesafe sql query builder) via the kysely-d1 3rd party dialect. https://github.com/kysely-org/kysely https://github.com/aidenwallis/kysely-d1

Interesting. Have you tried https://github.com/kysely-org/kysely ? I know Prisma is an ORM and kysely is a "type-safe typescript SQL query builder" but I just wanted to know if you had the opportunity to try it and your opinion about it. I'm searching for SQL typescript tooling for my next project.

Me too! Here are more tRPC-like projects: - ts-rest (https://ts-rest.com) - Garph (https://github.com/stepci/garph) - zodios (https://www.zodios.org) - Kysely (https://github.com/koskimas/kysely)

Kysely[1] and zapatos[2] are excellent solutions for type-safe typescript query builders. It’s hard to go back to the days of spending 20-30% of your time in the object mapping layer. [1] https://github.com/koskimas/kysely [2] https://github.com/jawj/zapatos

No, he's stated somewhere in the issue tracker that he has no plans to ever do this. edit: here - https://github.com/koskimas/kysely/issues/162#issuecomment-1...

Dang, how do they implement the “parse text strings and generate types immediately available in auto-complete” thing?? I can see how you could do that with Rust Macros, but how do they do it in TS? Eg. this thing: blah.select(['pet.name as pet_name']) is inferred to return a type with a `pet_name` field, parsing the contents of the SQL expression? [Update]: whatafak lol TS has way more juice in it than I realized: https://github.com/koskimas/kysely/blob/master/src/parser/se...