Knex
kysely-codegen
Knex | kysely-codegen | |
---|---|---|
95 | 9 | |
18,758 | 619 | |
0.6% | - | |
7.9 | 8.7 | |
3 days ago | 14 days ago | |
JavaScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Knex
-
JavaScript Libraries for Implementing Trendy Technologies in Web Apps in 2024
Knex.js
-
Create a Blog web app using Adonis.js 6
AdonisJS core team has created/maintains Lucid. It is a SQL query builder, and an Active Record ORM built on top of Knex.
-
Type-safe Data Access in Go using Prisma and sqlc
Now, why not use an ORM? I've seen performance issues too many times with ORMs. I prefer writing my own SQL to avoid surprises. After all, I know the database schema and writing code for a specific purpose very often leads to better performance than generic code. ORMs have to support all kinds of database schemas. I only have to support mine. Having successfully used Knex.js in NodeJS (a popular query builder) in the past, I know writing SQL queries myself is not hard and provides very good performance.
-
Can I create another WordPress that satisfies humanity?
Given the dynamic nature of the schema, we employ Knex, a query builder, for database access.
-
What's wrong with Node.js ORMs? Thousands of issues? Why?
https://www.npmjs.com/package/knex - 779 issues
- Knex 3.0
-
Plankaban Raspberry Pi 4 Setup Help
# related: https://github.com/knex/knex/issues/2354
-
Credentials Leak with Knex
This article will be focused on a security issue that I found in Knex and how to mitigate it, but I'll also talk briefly about the social aspects of this problem.
- [Node] Knex.js: comment correctement chaîner et utiliser .First () pour interroger?
-
Why SQL is right for Infrastructure Management
SQL is an old, irregular language to work with, but it is better known than HCL and SQL already has it's own Pulumi/CDK in the form of every ORM with introspection (like Javascript's Prisma, Python's Django, Go's XO etc) and QueryBuilder (LINQ, Knex, etc) in whatever programming language you prefer. You probably already know it.
kysely-codegen
-
Show HN: Tsynamo – Type-friendly DynamoDB query builder for TypeScript
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 library in use yet, but you can get the library's main idea from there.
Since the project is still in its early stages, it doesn't yet have 100% support for all DynamoDB features, like querying indexes. The next steps will be increasing the support coverage and perhaps adding automatic type generation as inspired by kysely-codegen (https://github.com/RobinBlomberg/kysely-codegen).
Would love to get some feedback, thanks in advance!
-
Simple CQRS in NodeJS with Typescript
Querying the database (PostgreSQL) should not be ground breaking. Personally I like to have full type-safety so we can easily catch bugs during the development time without introducing any tests that are just testing the data type from our datastore to match the data type our API expects. I like to go database schema first, which means that we generate types from the database schema and work with those. Any change to the schema of the database is made with SQL migrations and after that, the typescript types are regenerated. Another approach is to use a code-first tool like TypeORM or Prisma. However in my experience such tools often produce not efficient SQL queries and are less easy to extend. In my projects I use library kysely (https://github.com/koskimas/kysely) with kysely-codegen (https://github.com/RobinBlomberg/kysely-codegen) to have a full type-safe SQL builder.
-
Kysely: TypeScript SQL Query Builder
The main difference to me is that with Prisma I don't need to do any SQL to get a project up and running. I can define the tables and relations from my code or from Prisma Studio, and in one swoop I get the db structure done and the types defined.
I know my way around a database, but I'd rather not leave my code editor whenever I need to add a new column to a table.
With Kysely you have to create the DB schema, and then write the types; with every change you need, you gotta do both again.
(At least this seems true by default; as the project's readme mentions, there is a code generator[1] to generate the types from the DB schema; not quite the same but at least it's better than nothing.)
Commenters say that writing complex queries with Kysely is easier, which makes me wonder if I could use Prisma except for those, since Kysely should be able to just generate the SQL query for me to handle to Prisma...
[1]: https://github.com/RobinBlomberg/kysely-codegen
-
Allow Cloudflare D1 to be used like an O/R mapper with type-safe
kysely kysely-codegen kysely-d1 allows access to D1 while using SQL Builder.
-
Well, shit. Objection.js has been sunset, which ORM/querybuilder did you move to?
For what it's worth, I've been using kysely-codegen to generate the types based on the database schema and it's been working great for me.
-
ADVICE WANTED - Typescript PostgreSQL without ORM
I dislike ORMs and have been using Kysely https://github.com/koskimas/kysely and https://github.com/RobinBlomberg/kysely-codegen for a small project and so far I love it. It's a mapper/query builder that is equivalent to Dapper in C# (without the query builder) but with the power of typescript's type system to enforce proper queries. You can also bypass something with the sql to write raw SQL.
- The PlanetScale serverless driver for JavaScript
- Closest library/setup/configuration to JOOQ?
What are some alternatives?
Prisma - Next-generation ORM for Node.js & TypeScript | PostgreSQL, MySQL, MariaDB, SQL Server, SQLite, MongoDB and CockroachDB
Sequelize - Feature-rich ORM for modern Node.js and TypeScript, it supports PostgreSQL (with JSON and JSONB support), MySQL, MariaDB, SQLite, MS SQL Server, Snowflake, Oracle DB (v6), DB2 and DB2 for IBM i.
slonik - A Node.js PostgreSQL client with runtime and build time type safety, and composable SQL.
pg-promise - PostgreSQL interface for Node.js
kysely-data-api
TypeORM - ORM for TypeScript and JavaScript. Supports MySQL, PostgreSQL, MariaDB, SQLite, MS SQL Server, Oracle, SAP Hana, WebSQL databases. Works in NodeJS, Browser, Ionic, Cordova and Electron platforms.
kysely - A type-safe typescript SQL query builder [Moved to: https://github.com/kysely-org/kysely]
ts-sql-query - Type-safe SQL query builder like QueryDSL or JOOQ in Java or Linq in .Net for TypeScript with MariaDB, MySql, Oracle, PostgreSql, Sqlite and SqlServer support.
kysely-d1 - D1 dialect for Kysely