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
While CockroachDB (CRDB) offers a mostly PostgreSQL-compatible API, Bytebase isn't compatible due to the fact it relies on functions such as pg_table_size() that unfortunately do not exist in CRDB.
This makes the tool completely incompatible with CRDB due to its inability to list tables since the getListTableQuery function in backend/plugin/db/pg/sync.go depends on these PSQL-only functions:
Describe the solution you'd like
I can imagine two solutions to make Bytebase compatible with CockroachDB:
Detect CockroachDB as a special flavor of PostgreSQL, like you have a version check.
Add CockroachDB as a separate database with its own driver, most of it could be copied.
It would certainly be cleaner to integrate CockroachDB as a separate database since its API is mostly compatible but doesn't use PostgreSQL at all under the hood. They still have many unsupported features, but for the ones they have you can definitely port them over from the existing PostgreSQL driver.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
While CockroachDB (CRDB) offers a mostly PostgreSQL-compatible API, Bytebase isn't compatible due to the fact it relies on functions such as pg_table_size() that unfortunately do not exist in CRDB.
This makes the tool completely incompatible with CRDB due to its inability to list tables since the getListTableQuery function in backend/plugin/db/pg/sync.go depends on these PSQL-only functions:
Describe the solution you'd like
I can imagine two solutions to make Bytebase compatible with CockroachDB:
It would certainly be cleaner to integrate CockroachDB as a separate database since its API is mostly compatible but doesn't use PostgreSQL at all under the hood. They still have many unsupported features, but for the ones they have you can definitely port them over from the existing PostgreSQL driver.
Additional context
No response
The text was updated successfully, but these errors were encountered: