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
Is your feature request related to a problem? Please describe.
This is a feature.
Postgres is a great database, however it's a SPOF. Both cockroachdb and yugabyte are solutions for this issue.
Unfortunately neither support xid8 type.
I do see that SpiceDB (to support cockroachdb) uses a normal timestamp to sidestep this issue.
Describe the solution you'd like
Would be awesome if both cockroachdb and yugabyte are supported to give others options. Looking at the migration files, once one is completed. It's a copy and paste for the other.
Additional context
Would the work entail?
Creating a new folder in the internal / storage directory with migrations tailored for another database.
Changing migration.go to support the other engines.
Changing the database interactivity insert/update/delete to support the other engines?
I suspect it could be a minimal change, due to both databases mimic a postgres connection?
Thanks!
The text was updated successfully, but these errors were encountered:
I've added [yugabyte] as a new engine and have found the relevant functions and types (that required minimum 12/13) for version 11. Hopefully this won't cause any unnecessary conflicts or issues.
Is your feature request related to a problem? Please describe.
This is a feature.
Postgres is a great database, however it's a SPOF. Both cockroachdb and yugabyte are solutions for this issue.
Unfortunately neither support xid8 type.
I do see that SpiceDB (to support cockroachdb) uses a normal timestamp to sidestep this issue.
Describe the solution you'd like
Would be awesome if both cockroachdb and yugabyte are supported to give others options. Looking at the migration files, once one is completed. It's a copy and paste for the other.
Additional context
Would the work entail?
I suspect it could be a minimal change, due to both databases mimic a postgres connection?
Thanks!
The text was updated successfully, but these errors were encountered: