Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problems Reverse Engineering MAXDB Schema #124

Open
demarco88 opened this issue Apr 18, 2024 · 0 comments
Open

Problems Reverse Engineering MAXDB Schema #124

demarco88 opened this issue Apr 18, 2024 · 0 comments

Comments

@demarco88
Copy link

demarco88 commented 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:

  1. 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
  2. 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)
  3. 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

@demarco88 demarco88 changed the title Codepage Support Problems Reverse Engineering MAXDB Schema Apr 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant