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
Hi. I'm not very familiar with liquibase, but I did a reverse engeneering test on a large maxdb database. It looks very good expect a few thinks:
The reverse engineering definition generates not the right legnth of all char/varchar columns. F.e. the src table "KEY" VARCHAR (7) UNICODE not null and Dest "KEY" VARCHAR (1) ASCII not null
Futher some column attributes are ignored: We have several columns which are UNICODE columns in the src-db. In destination db these columns defined ASCII (see example above)
Not a big problem but fy.i: We have a table which contains a column named "timestamp" which cannot be created on the destination database (src and dest are maxdb). Reserved word....
thx and best regards
Marco
The text was updated successfully, but these errors were encountered:
demarco88
changed the title
Codepage Support
Problems Reverse Engineering MAXDB Schema
Apr 18, 2024
Hi. I'm not very familiar with liquibase, but I did a reverse engeneering test on a large maxdb database. It looks very good expect a few thinks:
"KEY" VARCHAR (7) UNICODE not null
and Dest"KEY" VARCHAR (1) ASCII not null
thx and best regards
Marco
The text was updated successfully, but these errors were encountered: