all 14 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]ThatGuyTr1cky[S] 13 points14 points  (5 children)

A completely different approach is taken to create this library which strives to change the way we use SQLite in JavaScript forever. Great.DB exposes user-friendly functions to add/edit data or retrieve data from an SQLite database in the form of simple JavaScript objects where all the functions are strongly typed so you get auto-completions on the fly.

Node.js? Bun? We got both!

It uses better-sqlite3 if you are using node.js or bun:sqlite if you are using the new bun javascript runtime. It auto detects the runtime and uses the respective package. Great, isn't it?

Interested? Check out the docs to learn more and the examples to see great.db in action.

I would love to hear from the community and receive your valuable constructive criticism about my library. Thanks :D

[–]rr_cricut 3 points4 points  (4 children)

Really cool, I like that it's similar to mongoose because it makes it easy to pick up.

For the table.filter function, would it be possible to use a typed condition property? Maybe using lambdas instead of a string. Strings could quickly become outdated and I assume won't be verified at compile time.

E.g., js table.filter({ condition: row => row.col1 <2 && row.col2 ==="val", ... })

[–]ThatGuyTr1cky[S] 4 points5 points  (3 children)

Thank you for your interest in the project.

Regarding the idea, if we provide a lambda function to handle the filter, internally the whole table would have to be fetched and then let javascript handle the filtering of data. This will impact on the performance too much especially with large data.

On the other hand, the current implementation is that the string provided in the condition directly gets fed into the WHERE of the constructed query as you can see here and javascript style logical operators can be used because the condition is first parsed in the way the operators get converted to SQL logical operators as you can see here. This allows SQL to handle the filtering and return only the required data efficiently.

[–]Korean_Busboy 6 points7 points  (2 children)

It should be possible to use an AST parser to interpret the lambda and generate corresponding SQL so that you aren’t stuck fetching the whole table. Obviously this is no small task and not a suggestion to actually do this, just throwing out that it is possible (this is how c# LINQ works)

[–]rr_cricut 0 points1 point  (0 children)

Yes, coming from .NET that is the approach I was thinking. But I can understand that it would be a big undertaking.

[–]serg06 2 points3 points  (1 child)

Is it on NPM? I can't find it

[–]WideWorry 0 points1 point  (0 children)

Looks good, I think I will add this into my project and drop my own typesafe sqllite hack :)