-
-
Notifications
You must be signed in to change notification settings - Fork 118
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
liquibase.exception.MigrationFailedException when importing generated XML files with dates #100
Comments
Thanks for the issue report. According to the documentation page: This is not quite what Jailer generates. Could you please check if the following can be imported?
Thanks in advance, |
The following error is logged:
This changeset is successful, though:
|
Where is the difference between the changeSet I asked you to test and this one? |
The valueDate pattern you provided separates the time by |
OMG, now I see that too. Please excuse my temporary blindness. It's good that there is no need to fall back to "value" attribute. That would probably cause problems with other DBMS. Liquibase can obviously handle a date in the format it expects correctly. I will correct this ASAP. I plan to release a new version at the end of the week. This issue will be fixed in the new version too. |
Fixed in Release 14.2 |
Description of the Issue
I am using the API to generate a liquibase XML file, but when I execute
mvn liquibase:update
, the following error is logged:XML file generated via API:
Expected Behavior
The insert will work if the "value" attribute is used instead of "valueDate":
<column name="created" value="2019-04-26-15.47.11"/>
The text was updated successfully, but these errors were encountered: