formatted sql changes not processed if file extension is not .sql
Description
In a database change log I try to include a formatted sql file:
<include file="db/t4.tab" />
"t4.tab"
--liquibase formatted sql
--changeset myname:431
create table t4(
id integer,
myname varchar2( 100 ),
myvalue number
);
-- rollback drop table t4 purge;
But it doesn't process the change appropriately (it's not reflected in database at all, nor an error is reported).
Seems it check for t4.tab file existence - if file is missing it fails with error.
If I rename the file to .sql - the change is applied as expected:
<include file="db/t4.sql" />
— So - for some reason, the file extension does matter. It's not acceptable to rename all scripts to *.sql since we have convention for file extensions based on database object types.
Environment
Linux
Activity
Show:
Nathan Voxland June 12, 2013 at 9:34 PM
Currently the logic for the type of file liquibase expects is extension based. It may be worth making that smarter
In a database change log I try to include a formatted sql file:
<include file="db/t4.tab" />"t4.tab"
--liquibase formatted sql --changeset myname:431 create table t4( id integer, myname varchar2( 100 ), myvalue number ); -- rollback drop table t4 purge;But it doesn't process the change appropriately (it's not reflected in database at all, nor an error is reported).
Seems it check for t4.tab file existence - if file is missing it fails with error.
If I rename the file to .sql - the change is applied as expected:
<include file="db/t4.sql" />—
So - for some reason, the file extension does matter. It's not acceptable to rename all scripts to *.sql since we have convention for file extensions based on database object types.