Would love to see this :)

Ah nice, hey @AustinGil !

Kinda surprised, I did some googling after seeing your comment--one of the blockers here was lack of sequences in sqlite, but turns out sqlite's autoincrement primary keys have an internal sqlite_sequence table that can very likely be used (carefully, pending more research) to mimic Joist's up-front/pre-INSERT assignment of entity ids, which was one of the pg-isms that would be ~not-hard-but-annoying to move away from:

sqlite> create table bar (id integer primary key autoincrement);
sqlite> insert into bar (id) values (null);
sqlite> select * from bar;
1
sqlite> select * from sqlite_sequence;
bar|1
-- pretend joist bulk pre-assigns 10 new ids for bar entities 
sqlite> update sqlite_sequence set seq = 10;
sqlite> insert into bar (id) values (null);
sqlite> select * from bar;
1
11

So pulling the metadata from the SQLite schema is probably the biggest blocker at this point.

Yeah, I wish I knew more about db adapters so I could be of service, but I'm more of a frontend guy. Trying to find an ORM I really like, and hopefully one that works with SQLite. I listened to the JS Party on this one and it sounds great.

Np! Especially for the first one or two "not postgres" adapters, it will likely be something myself/one of our core maintainers will need to do, just to even get Joist's adapter layer setup well to really do "more than just postgres".

I did some more googling and really seems like the blocker is finding a "pg-structure but for sqlite"--like this sqlite_master table will tell you all of the tables in the database, but to get the columns / foreign keys / etc., you have to parse the CREATE TABLE DDL. Which just doesn't sound like fun... And I haven't found anything on npm that will do it for us.