You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Joist's core model is generally very database-agnostic; the main things that need tackled to support a non-pg database would be:
Decouple schema information gathering from pg-structure, which is excellent but pg-only; we'd need like a "db-structure" that supports multiple dbs
Rework em.flush to support INSERTs without sequences--currently Joist uses sequences to bulk-assign ids and then do INSERTs/UPDATEs in a dumb/naive order; if we must do the INSERT to know the key, like in MySQL, then that logic needs refactored.
Potentially rework em.flush to not rely on deferred foreign keys--currently Joist uses Postgres's deferred foreign keys to, like the previous point, do INSERTs/UPDATEs in a dumb/naive order.
The text was updated successfully, but these errors were encountered:
stephenh
changed the title
Generalize to other databases
Support other databases
May 7, 2023
Joist's core model is generally very database-agnostic; the main things that need tackled to support a non-pg database would be:
Decouple schema information gathering from pg-structure, which is excellent but pg-only; we'd need like a "db-structure" that supports multiple dbs
Rework
em.flush
to supportINSERT
s without sequences--currently Joist uses sequences to bulk-assign ids and then do INSERTs/UPDATEs in a dumb/naive order; if we must do theINSERT
to know the key, like in MySQL, then that logic needs refactored.Potentially rework
em.flush
to not rely on deferred foreign keys--currently Joist uses Postgres's deferred foreign keys to, like the previous point, do INSERTs/UPDATEs in a dumb/naive order.The text was updated successfully, but these errors were encountered: