Liquibase 3.2.2, DB : Vertica 7.1 : defaultSchemaName not used to create tables

General Discussion
1

Hello,



I have an issue when using parameter defaultSchemaName. Except Liquibase
tables, Tables are created in default schema of username and not in .defaultSchemaName.

Here are the logs :

DEBUG
1/20/15 10:15 AM: liquibase: Executing QUERY database command:
SELECT LOCKED FROM vddbadev2.DATABASECHANGELOGLOCK WHERE
ID=1
DEBUG 1/20/15 10:15 AM: liquibase: Lock
Database
DEBUG 1/20/15 10:15 AM: liquibase: Executing UPDATE
database command: UPDATE vddbadev2.DATABASECHANGELOGLOCK SET LOCKED
= TRUE, LOCKEDBY = ‘vd2263.angers.cnp.fr (158.157.108.11)’,
LOCKGRANTED = ‘2015-01-20 10:15:29.803’ WHERE ID = 1 AND
LOCKED = FALSE
INFO 1/20/15 10:15 AM: liquibase: Successfully
acquired change log lock
DEBUG 1/20/15 10:15 AM: liquibase:
Resolving XML entity name=‘null’, publicId=‘null’,
baseURI=‘null’,
systemId=’<a href=‘http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-2.0.xsd’’ target=’_blank’>http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-2.0.xsd’
DEBUG
1/20/15 10:15 AM: liquibase: Found namespace details class
liquibase.parser.core.xml.StandardNamespaceDetails for
http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-2.0.xsd
DEBUG
1/20/15 10:15 AM: liquibase: Local path for
http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-2.0.xsd is
liquibase/parser/core/xml/dbchangelog-2.0.xsd
DEBUG 1/20/15
10:15 AM: liquibase: Successfully loaded XSD from
liquibase/parser/core/xml/dbchangelog-2.0.xsd
DEBUG 1/20/15
10:15 AM: liquibase: Resolving XML entity name=‘null’,
publicId=‘null’, baseURI=‘null’,
systemId=’<a href=‘http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-2.0.xsd’’ target=’_blank’>http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-2.0.xsd’
DEBUG
1/20/15 10:15 AM: liquibase: Found namespace details class
liquibase.parser.core.xml.StandardNamespaceDetails for
http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-2.0.xsd
DEBUG
1/20/15 10:15 AM: liquibase: Local path for
http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-2.0.xsd is
liquibase/parser/core/xml/dbchangelog-2.0.xsd
DEBUG 1/20/15
10:15 AM: liquibase: Successfully loaded XSD from
liquibase/parser/core/xml/dbchangelog-2.0.xsd
DEBUG 1/20/15
10:15 AM: liquibase: Executing QUERY database command: SELECT MD5SUM
FROM vddbadev2.DATABASECHANGELOG WHERE MD5SUM IS NOT NULL
INFO
1/20/15 10:15 AM: liquibase: Reading from
vddbadev2.DATABASECHANGELOG
DEBUG 1/20/15 10:15 AM: liquibase:
Executing QUERY database command: SELECT
FILENAME,AUTHOR,ID,MD5SUM,DATEEXECUTED,ORDEREXECUTED,EXECTYPE,DESCRIPTION,COMMENTS,TAG,LIQUIBASE
FROM vddbadev2.DATABASECHANGELOG ORDER BY DATEEXECUTED ASC,
ORDEREXECUTED ASC
DEBUG 1/20/15 10:15 AM: liquibase: Executing
QUERY database command: select count(*) from
vddbadev2.DATABASECHANGELOGLOCK
DEBUG 1/20/15 10:15 AM:
liquibase: ./dbchangelog.xml:
0.0.0-0.1.0/dbchangelog_0.0.0-0.1.0.xml::1::MFI: Computed checksum
for as d41d8cd98f00b204e9800998ecf8427e
DEBUG 1/20/15 10:15
AM: liquibase: ./dbchangelog.xml:
0.0.0-0.1.0/dbchangelog_0.0.0-0.1.0.xml::2::MFI: Computed checksum
for tagDatabase:[
tag=“R_0.0.0”
] as
61e85b5b7cc792f6b29b7db13caf7709
DEBUG 1/20/15 10:15 AM:
liquibase: ./dbchangelog.xml:
0.0.0-0.1.0/dbchangelog_0.0.0-0.1.0.xml::2::MFI: Computed checksum
for 7:61e85b5b7cc792f6b29b7db13caf7709: as
69f70b61ff88387e9d518bd47d5c1406
DEBUG 1/20/15 10:15 AM:
liquibase: ./dbchangelog.xml:
0.0.0-0.1.0/dbchangelog_0.0.0-0.1.0.xml::3::MFI: Running
Changeset:0.0.0-0.1.0/dbchangelog_0.0.0-0.1.0.xml::3::MFI
DEBUG
1/20/15 10:15 AM: liquibase: ./dbchangelog.xml:
0.0.0-0.1.0/dbchangelog_0.0.0-0.1.0.xml::3::MFI: Changeset
0.0.0-0.1.0/dbchangelog_0.0.0-0.1.0.xml::3::MFI
DEBUG 1/20/15
10:15 AM: liquibase: ./dbchangelog.xml:
0.0.0-0.1.0/dbchangelog_0.0.0-0.1.0.xml::3::MFI: fichier :
01_TAB_MFI_RUN_EXECUTE.sql
DEBUG 1/20/15 10:15 AM: liquibase:
./dbchangelog.xml: 0.0.0-0.1.0/dbchangelog_0.0.0-0.1.0.xml::3::MFI:
Reading ChangeSet:
0.0.0-0.1.0/dbchangelog_0.0.0-0.1.0.xml::3::MFI
DEBUG 1/20/15
10:15 AM: liquibase: ./dbchangelog.xml:
0.0.0-0.1.0/dbchangelog_0.0.0-0.1.0.xml::3::MFI: Executing
Statement: liquibase.statement.core.RawSqlStatement
DEBUG
1/20/15 10:15 AM: liquibase: ./dbchangelog.xml:
0.0.0-0.1.0/dbchangelog_0.0.0-0.1.0.xml::3::MFI: Executing EXECUTE
database command: create table MFI_RUN_EXECUTE



I’m using Liquibase 3.2.2 with Vertcia extension 1.2



Can anyone help me on this ?



Regards,

Mohamed Boutkhil


2

Hi,

Sorry for the late response - i missed your post.

I think this is due to the parameter not updating the search_path so that all new tables will use the default parameter.

I’ll try to patch up the extension and upload a new version.

in any case you can directly specify the schema name in the change (although redundant…)

p.s. if you have issues related to the extension, feel free to mail me at cohenjo@hp.com

I don’t always follow the forum - sorry.

Regards,

Jony