News for hackers. Stuff that matters.
Re:SQLite JSON at Full Index Speed Using Generated Columns by focusgroup0 on Friday December 12, 2025 @11:41AM (#46245813)
Would this be a good fit for migrating from mongo --> sqlite? A task I am dreading
Re:SQLite JSON at Full Index Speed Using Generated Columns by zffr on Friday December 12, 2025 @12:15PM (#46246171)
Just curious, why do you want to migrate from mongo (document database server) to sqlite (relational database library)?

That migration would be making two changes: document-based -> relational, and server -> library.

Have you considered migrating to Postgres instead? By using another DB server you won't need to change your application as much.

Re:SQLite JSON at Full Index Speed Using Generated Columns by focusgroup0 on Friday December 12, 2025 @02:20PM (#46247680)
Thanks for the feedback. The document model in mongo was slopped together by a junior engineer, so perhaps an unorthodox approach. It is basically flat, and already used in a pseudo-relational manner via in-app join to the existing sqlite store. This blog post inspired me to think, what if we just chucked all the json from mongo into sqlite and used the generated indices? Then we can gradually "strangler fig" endpoint by endpoint
Re:SQLite JSON at Full Index Speed Using Generated Columns by rglynn on Saturday December 13, 2025 @03:55AM (#46253156)
This sounds roughly on-track, but I agree with GP; Postgres would probably be better (also has great JSON(B) support).