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

LONG VARCHAR / LONG VARBINARY are not detected as CLOB / BLOB #4669

Closed
2 tasks done
mkarg opened this issue Aug 14, 2023 · 0 comments · Fixed by #4670
Closed
2 tasks done

LONG VARCHAR / LONG VARBINARY are not detected as CLOB / BLOB #4669

mkarg opened this issue Aug 14, 2023 · 0 comments · Fixed by #4670

Comments

@mkarg
Copy link
Contributor

mkarg commented Aug 14, 2023

Search first

  • I searched and no similar issues were found

Description

liquibase update apparently does not correctly detect the types LONG VARCHAR, LONG NVARCHAR, LONG BINARY and LONG VARBINARY as CLOB / BLOB. Instead, it detects it as "Unknown" type. As a result, such a schema applied upon a RDBMS that does not know that type names (but does know that types using a different name) will fail.

Steps To Reproduce

  1. SQL Anywhere:
CREATE TABLE T (C LONG VARCHAR)
liquibase generateChangelog
  1. PostgreSQL:
liquibase update

Expected/Desired Behavior

BLOB / CLOB should get detected.

Liquibase Version

master

Database Vendor & Version

SAP SQL Anywhere 17.0.11, PostgreSQL 15.3

Liquibase Integration

N/A

Liquibase Extensions

N/A

OS and/or Infrastructure Type/Provider

Windows 10 Pro (German)

Additional Context

N/A

Are you willing to submit a PR?

  • I'm willing to submit a PR (Thank you!)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants