I'm using Liquibase through the maven plugin (3.0.8). In my liquibase.properties file I have decleared: defaultSchemaName=TEST
That schema exists in the H2 database, but when liquibase runs DB update it doesn't create tables under the declared schema (refer to liquibase_3_not_using_test_schema.png).
if I simply change <version>3.0.8</version> to <version>2.0.5</version> in my pom.xml, then the tables are created under the correct schema (refer to liquibase_2_using_test_schema.png).
Here's a sample of how I'm creating a table (I'm not using schemaName attribute of createTable and would like to continue not using it, as it works in 2.0.5): <changeSet author="poolik" id="test-table"> <createTable tableName="EVENT"> <column name="ID" type="BIGINT(19)"> <constraints nullable="false"/> </column> </createTable> </changeSet>
My question is, should I be configuring something differently in 3.0.8 or is there a bug in 3.0.8 and defaultSchemaName is somehow ignored?
Environment
jdk 1.7, os x 10.9, H2 1.3.174, Liquibase 3.0.8
Attachments
2
14 Dec 2013, 02:14 PM
14 Dec 2013, 02:14 PM
Activity
Show:
Nathan Voxland May 28, 2014 at 8:32 PM
It is working correctly for me in 3.2.0. I've done some work around default schema handling so that probably resolved it earlier.
I'm using Liquibase through the maven plugin (3.0.8). In my liquibase.properties file I have decleared:
defaultSchemaName=TEST
That schema exists in the H2 database, but when liquibase runs DB update it doesn't create tables under the declared schema (refer to liquibase_3_not_using_test_schema.png).
if I simply change <version>3.0.8</version> to <version>2.0.5</version> in my pom.xml, then the tables are created under the correct schema (refer to liquibase_2_using_test_schema.png).
Here's a sample of how I'm creating a table (I'm not using schemaName attribute of createTable and would like to continue not using it, as it works in 2.0.5):
<changeSet author="poolik" id="test-table">
<createTable tableName="EVENT">
<column name="ID" type="BIGINT(19)">
<constraints nullable="false"/>
</column>
</createTable>
</changeSet>
My question is, should I be configuring something differently in 3.0.8 or is there a bug in 3.0.8 and defaultSchemaName is somehow ignored?