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
I tried using the schema sync in the hosted version, was getting 502 errors.
So I tried the same in self-host version and I got the same error, but this time I could see this in the docker logs:
Failed to compute diff between source and target schemas, error: failed to parse and preprocess old statements
Followed by what appears to be a schema dump of the entire database.
The schema diff is being done between 2 databases on the same instance. Both are PostGIS-enabled databases if that makes any difference.
PostGIS version: 3.4.0
Steps to reproduce
Sync Schema
Select source schema
Select target databases
Expected behavior
Show Schema changes
Provide the database you are using
PostgreSQL 12.16 (Ubuntu 12.16-1.pgdg20.04+1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0, 64-bit
Provide the version control system you are using
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Provide the Bytebase version you are using
2.14.1
Describe the bug
I tried using the schema sync in the hosted version, was getting 502 errors.
So I tried the same in self-host version and I got the same error, but this time I could see this in the docker logs:
Failed to compute diff between source and target schemas, error: failed to parse and preprocess old statements
Followed by what appears to be a schema dump of the entire database.
The schema diff is being done between 2 databases on the same instance. Both are PostGIS-enabled databases if that makes any difference.
PostGIS version: 3.4.0
Steps to reproduce
Expected behavior
Show Schema changes
Provide the database you are using
PostgreSQL 12.16 (Ubuntu 12.16-1.pgdg20.04+1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0, 64-bit
Provide the version control system you are using
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: