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

Prevent having to match database queries #204

Closed
ra0x3 opened this issue Sep 11, 2022 · 0 comments · Fixed by #203
Closed

Prevent having to match database queries #204

ra0x3 opened this issue Sep 11, 2022 · 0 comments · Fixed by #203

Comments

@ra0x3
Copy link
Contributor

ra0x3 commented Sep 11, 2022

  • After New sqlite support #134 we now have support for two database types: Postgres, Sqlite
  • Each database is currently split into it's own crate
    • They behave very similarly but have some slight differences
  • Currently when having to execute a statement, we're match'ing the database type
  • This works fine, but requires quite a bit of boilerplate (especially for slightly more involved queries)
  • It would be great if we could create a proxy component that uses a single interface to interact with the data layer, regardless of which database is being used

Additional context:

So instead of:

@ra0x3 ra0x3 closed this as completed Sep 11, 2022
@ra0x3 ra0x3 reopened this Sep 11, 2022
@ra0x3 ra0x3 linked a pull request Sep 11, 2022 that will close this issue
12 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant