Just added a Jira ticket for this issue
Just added a Jira ticket for this issue
I haven’t yet. I have a few other changes to work through first, so it will probably be at least a week or so until I can get to it. Hopefully the fix will be in beta2.
Nathan
Hi Nathan,
did you have had the chance to dig into the issue with Firebird and Liquibase 3.0 beta?
During the weekend I have tied to studi the sources but to no avail: unfortunately java is not my primary language so I give up
–
fabio vitale
Thank you Nathan: I’ll wait for your investigations
Hi, I’m trying to issue the following update command that works perfectly on Liquibase 2.x
liquibase --changeLogFile=db.changelog.001.xml ^
update
--------------------------
this is the xml file:
--------------------------
<databaseChangeLog
xmlns=“http://www.liquibase.org/xml/ns/dbchangelog”
xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”
xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog
http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-3.0.xsd">
CREATE DOMAIN D_PK AS
BIGINT
NOT NULL;
CREATE or alter trigger department_bi for department
active before insert position 0
as
begin
if (new.id is null) then
new.id = gen_id(gen_department_id,1);
end
-----------------------------
This is the error log:
-----------------------------
DEBUG 13/02/13 18.11:liquibase: Unable to load/access Apache Derby driver class to check version
DEBUG 13/02/13 18.11:liquibase: Connected to SYSDBA@jdbc:firebirdsql:java://localhost:3050/c:/liquibase.fdb
DEBUG 13/02/13 18.11:liquibase: Not adjusting the auto commit mode; it is already true
SEVERE 13/02/13 18.11:liquibase: Unknown Reason
liquibase.exception.DatabaseException: java.lang.NullPointerException
… 2 more
---------------------------------------------
This is my liquibase.properties
---------------------------------------------
#liquibase.properties
driver: org.firebirdsql.jdbc.FBDriver
classpath: jaybird-full-2.2.2.jar
url: jdbc:firebirdsql://localhost:3050/c:/liquibase.fdb
username: SYSDBA
password: masterkey
logFile=logFile.log
logLevel=debug
It looks like a problem with firebird support. That isn’t a database I’ve been able to test yet, unfortunately and it looks like there is a problem with the catalog/schema management.
I’ll have to look into it.
Nathan
This is great!
I really appreciate all the new features in in v 3.0: you have done a wonderful job.
Thank you so much Nathan!
–
fabio vitale