Re : Extension migration validation issue 3.1.1 -> 3.2.2
Never mind, the problem with the "minValue" Attribute was due to the fact that the setter for the variable in the class did not follow the Bean-contract. Everything seems fine now.
View ArticleRe : Extension migration validation issue 3.1.1 -> 3.2.2
Good, thanks for the update. Nathan
View ArticlePostgresql data type error creating xml
I have just ran my first generateChangeLog command without any notifications. When I tried to apply it to a new database and new schema I get the following error: myColumn FLOAT8(*, 17)): ERROR:...
View ArticleRe : Postgresql data type error creating xml
That may have been fixed in a later version. Are you running the newest 3.2.2? Nathan
View ArticleRe : Postgresql data type error creating xml
We are running 3.2.2, also I have verify the encoding and we are using UTF-8. Driver for postgres: postgresql-9.3-1102.jdbc41.jar. Java version 1.7.0
View ArticleRe : diff between current changelog and hibernate entities
It definitely could be done, I just haven't gotten to it yet. I'm in the middle of a large refactoring of the snapshot logic which will hopefully make it easier to implement as well. Nathan
View ArticleRe : What does liquibase validate really do, and when should I use it?
There should be no difference. The Liquibase.validate() method is called in both cases. UpdateSQL will also run validate just like update does, so updateSql should be sufficient. Nathan
View ArticleRe : precondition problem mysql
Yes, sequences are not supported by mysql which is causing the problem. Previous versions allowed it assuming you knew they wouldn't get created but a better route is to add a dbms attribute to...
View ArticleRe : Postgresql data type error creating xml
I see there is already an issue logged for it. https://liquibase.jira.com/browse/CORE-1956 I'm looking at data type and other snapshot logic with 3.3. For now, you will just have to fix up the...
View Articlecheck migration status without locking
Hi, i am using Liquibase via API aka Liquibase.class. Currently i am checking at login time if a DB upgrade is needed with listUnrunChangeSets(). This creates a lock for each check. Because this is...
View ArticleRe : check migration status without locking
some more info from me. I just digged through the code. I simply dont understand why a read-only operation like "listUnrunChangeSets" calls this method: public void checkLiquibaseTables(boolean...
View ArticleRe : check migration status without locking
I see that we are using a pretty old Liqibase (1.9.x) and that at least with 3.1.x the listUnrunChangeSets() no longer has a waitForLock() call. Perhaps i am chasing a phantom because of old version.
View ArticleTrack Database changes made with out using changeset
Hi All, How to keep track of changes made to a database that are done with out using the changesets. This is the scenario. Made Changes to database using changesets for release 1. Made another set of...
View ArticleRe : Track Database changes made with out using changeset
You could use the liquibase diff and diffchangeset commands to see what the changes are, or to generate a changeset that has the changes necessary to get the databases back in sync. Steve Donie...
View ArticleRe : Upgrade 3.1.1 to 3.2.0 throws...
After upgrading from 3.1.1 to 3.2.2, I still get this error: Caused by: org.soluvas.data.push.RepositoryException: Cannot migrate 'tuneeca' using 'id/co/bippo/inventory/inventorybalance.liquibase.xml':...
View ArticleRe : Track Database changes made with out using changeset
Thank you Steve, do i have to use both Diff and diffchangeset or just one of these. Most of the diff examples given were for comparing two database. but in my case its diff within a single database...
View ArticleRe : How to handle database changes made by an automatic upgrade script?
Hi XUn2, Even i have a similar situation. Did you find a solution to your question?
View ArticleRe : Upgrading from 2.0.5 to 3.2.0 - Problem with preConditions ?
Hi Nathan, I tested with the version 3.2.2 and is failing as well, but I think i know why is failing. Checking the code and running step by step i saw that the liquibase script was wrong (too bad...
View ArticleRe : Upgrading from 2.0.5 to 3.2.0 - Problem with preConditions ?
For now I found a work arround, and it is working fine: <changeSet id="fix_upgrade_version_liquibase" author="e-ballo"> <preConditions onFail="MARK_RAN" onErrorMessage="View...
View ArticleRe : Upgrading from 2.0.5 to 3.2.0 - Problem with preConditions ?
I also find this : <changeSet author="m-corrales" id="RENAME_PACKAGE_ITEMS_PRICE_IDS"> <preConditions onFail="MARK_RAN"> <columnExists schemaName="ATI" tableName="ATI_STM_PACKAGE_ITEMS"...
View Article