-
Notifications
You must be signed in to change notification settings - Fork 39
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
Column oracle clob issue #11
Comments
Looks like this has fixed this in a fork by @leonardseymore |
Please push the fix to master. I have 3.2.2 and the fix is not applied. same in InsertDataChange.class |
Merged in pull request liquibase/liquibase#257 for liquibase 3.3.0 |
Hello,
With the update table tag, when specify column of type="CLOB" this isn't handled correctly by liquibase and throws error. ORA-01704: string literal too long.
at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:62)
e.g:
lots of data goes here
]]>
This requires the oracle function to_clob() to be used.
http://docs.oracle.com/cd/B19306_01/server.102/b14200/functions182.htm
This is with the latest 3.2.0 version of liquibase
The text was updated successfully, but these errors were encountered: