Hi,
just a short question:
When I reverse engineer a Oracle database table with a varchar2 column, I get a column type that includes VARCHAR2 and even the CHAR parameter (if the column was defined as CHAR and not as BYTE).
This is great for Oracle databases!
<createTable tableName=“SOME_TABLE”>
But if I try to run this against a postgres database, the script fails because postgres does not know the CHAR param.
The conversion from VARCHAR2 to VARCHAR is done correctyl in the generated postgres SQL but the CHAR param breaks it.
Is it possible to filter the CHAR param for databases that do not support ist?
Best regards,
Chris
-
Learn
-
Resources
-
Free Tools
OSS Risk Scanner Database DevOps Risk AssessmentCheat Sheets
Snowflake + Liquibase Databricks + Liquibase -
eBooks
6 Liquibase Community Risks & How to Avoid Guide: SOC 2 Compliance at the Database Layer Guide: Quantify the Value of Liquibase Secure -
Comparison Guides
Liquibase vs. Flyway Liquibase vs. Bytebase Liquibase Community vs Liquibase Secure
-
- Quickstart
- Get Started
- Documentation
- University
-
Resources
- Connect
- Contribute
- Join
- Blog