-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SQLite support #467
Comments
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 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 |
Just tracking what would be necessary, after a very small spike:
information_schema
, it has asqlite_master
that just as the raw DDL for each object, which would then need to be parsed :-|SEQUENCE
s, so would need to do INSERT+UPDATEsThe text was updated successfully, but these errors were encountered: