Skip to content
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

Support other databases #636

Open
stephenh opened this issue May 7, 2023 · 0 comments
Open

Support other databases #636

stephenh opened this issue May 7, 2023 · 0 comments

Comments

@stephenh
Copy link
Collaborator

stephenh commented 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:

  1. Decouple schema information gathering from pg-structure, which is excellent but pg-only; we'd need like a "db-structure" that supports multiple dbs

  2. 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.

  3. 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.

@stephenh stephenh changed the title Generalize to other databases Support other databases May 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant