-
Notifications
You must be signed in to change notification settings - Fork 39
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
Possible to support EdgeDB? #1979
Comments
ChiselStrike only supports SQLite and PostgreSQL right now and we don't unfortunately have plans to support other databases right now. Looking at EdgeDB, there seems to be some overlap with ChiselStrike and EdgeDB so I would be interested to hear how you'd see the integration happening? You'd define entities as |
Yes more I am thinking about it. I feel like I want to build my own version of ChiselStrike on top of edgedb. So use its schema but have easy way to define routes etc. Reason is that edgedb schema editor is just so great to use. For now I am trying both. EdgeDB shines in defining more complex relations between tables. Plus queries are easier. |
@nikitavoloboev We want to support more complex relationships in ChiselStrike schemas too, but just have not got around working on it beyond the simple ones. Is there something specific you're missing or is it an overall thing? I haven't tried out EdgeDB's schema editor (will do that) but we have so far been operating under the assumption that it's easy to define schemas with just TypeScript. |
How much does Chiselstrike depend on specifics of sqlite? Would it be possible in the future to support seamlessly switching in between databases and allow different developers to develop implementations for EdgeDB, MongoDB, GunDB i.e. like Prisma? |
I have my database use https://www.edgedb.com as I like their query language, query builders and schema. Its built on top of Postgres too.
I would love to try ChiselStrike but don't want to drop EdgeDB. Is it possible to support this use case?
Thank you.
The text was updated successfully, but these errors were encountered: