Support for cockroachdb #2689
Replies: 4 comments 9 replies
-
While it would be nice. I'm not really sure we can fully remove that. As the comment also mentions that it might be needed for that command to be included into the migrations it self. While, i think that command does work, since it did solve the foreign key constraint issues during migrations. It may be possible to create a special environment flag to exclude that command. When i have time i will try to see if i can do some testing. |
Beta Was this translation helpful? Give feedback.
-
@terribleplan, I think it will be a terrible plan (pun intended) to enable cockroache support. If i then export the schema of a running PostgresDB full DDL, and import that into the CockroachDB Vaultwarden at least seems to start. But i can't add a cipher, create an organization etc.. So, I'm not seeing this happening in the near future I'm afraid. |
Beta Was this translation helpful? Give feedback.
-
@BlackDex maybe YugabyteDB would be an alternative? It is more compatible with Postgresql. |
Beta Was this translation helpful? Give feedback.
-
So I noticed the "SET CONSTRAINTS ALL DEFERRED" statement was removed in a recent PR... I'll be trying Vaultwarden out on CockroachDb again soon |
Beta Was this translation helpful? Give feedback.
-
I was working on moving my installation and wanted to move from sqlite to cockroachdb for better redundancy (storing the rest of the files on network storage, so putting sqlite on that is problematic). Following the migration process outlined in the wiki I got to the point of starting vaultwarden targeting the new DB to run migrations, which failed as cockroach does not implement 100% of pg including
SET CONSTRAINTS ALL DEFERRED
. (Which according to this note doesn't actually do anything where the problem was first encountered)Is there any will or desire to support cockroach? It's mostly pg compatible and pretty easy to get a single-node instance running for testing.
Beta Was this translation helpful? Give feedback.
All reactions