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

Add support for SQLite as a additional datasource for the internal database #3055

Closed
Tracked by #3058 ...
silentninja opened this issue Jul 17, 2023 · 0 comments · Fixed by #3203
Closed
Tracked by #3058 ...

Add support for SQLite as a additional datasource for the internal database #3055

silentninja opened this issue Jul 17, 2023 · 0 comments · Fixed by #3203
Assignees
Labels
ready Ready for implementation type: enhancement New feature or request work: backend Related to Python, Django, and simple SQL
Milestone

Comments

@silentninja
Copy link
Contributor

silentninja commented Jul 17, 2023

Problem.

Our current installation process requires the user to set up a Postgres server, and a database in order to start Mathesar which adds more complexity to our installation process. While we provide a default Postgres server along with our docker-compose, other installation packages don't come with a default Postgres server.

Proposed solution

We should provide using SQLite as a datasource option for our internal database. This makes it easier for someone with an existing external Postgres database to try out Mathesar

Additional context

Postgres-specific field is used in only one place
https://github.com/centerofci/mathesar/blob/1d49c44d26ebcf7777b7ba29572f678930ba5942/mathesar/models/base.py#L890

Migration should be written to change the ArrayField to a JsonField with list as the default initializer. The migration should also take into consideration to move the existing data from the ArrayField into JsonField

@silentninja silentninja added type: enhancement New feature or request work: backend Related to Python, Django, and simple SQL ready Ready for implementation labels Jul 17, 2023
@silentninja silentninja added this to the v0.1.3 milestone Jul 17, 2023
@silentninja silentninja modified the milestones: v0.1.3, v0.1.4 Aug 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready Ready for implementation type: enhancement New feature or request work: backend Related to Python, Django, and simple SQL
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

1 participant