search

CSNW / sql-bricks

Transparent, Schemaless SQL Generation
http://csnw.github.io/sql-bricks
MIT License
203 stars 25 forks source link

Project Ownership / Maintenance #133

Open prust opened 1 year ago

prust commented 1 year ago

We no longer use this library much at CSNW. I'm still maintaining it at present, but I would love to hand it off if someone else is interested in taking ownership. The new owner would have complete control and could do whatever they want (code style, features, scope, etc). @Suor, is this something you would be interested in?

Suor commented 1 year ago

I don't use JavaScript much these days either. Supporting my libs the same way.

prust commented 1 year ago

@Suor: Good to know. Thanks!

quantuminformation commented 7 months ago

I use drizzle atm, any advantage with bricks?

prust commented 7 months ago

@quantuminformation: Drizzle looks great from the docs, it looks like it has some cool & powerful features that sql-bricks doesn't have (schema-based help & safety). There are some negative comments on Twitter, but I don't know if that's just par-for-the-course with social media, or if Drizzle has genuine problems. It looks actively maintained, which is a lot better than sql-bricks (I still maintain sql-bricks, but not very actively).

Scanning through the 485 open issues, I wonder if they allowed the scope of the project to grow bigger than their team can handle... but OTOH if you use it for mainstream databases & use-cases, that may not affect you.

At any rate, sql-bricks is a lot smaller & simpler, for better and for worse. It doesn't import a schema from your database and doesn't know your database's schema, so it won't check that the SQL it produces will actually work against your database, it only checks that it's valid SQL. And it won't type the data coming back for typescript consumers (I'm not sure if that's a Drizzle feature?). A contributor added TypeScript definitions for the API, but that's as far as the TypeScript support goes (not very far).

It has some adoption, but not enough to give a ton of confidence that most bugs have been found & fixed.

I think the only case where I would advise someone to choose sql-bricks over drizzle is if it was really important to them to find a "hackable" codebase that they can read, understand and adopt. And even there, the sql-bricks codebase isn't as "easy to understand & debug" as it once was (see https://github.com/CSNW/sql-bricks/issues/92). But it's much shorter than Drizzle's codebase, FWIW.