Liquibase single column changeset

Are you getting a stacktrace at all?

Nathan

no, thats part of the problem. liquibase is not very verbose with errors. the above is all i get, even with log-level set to debug. we are using ant to execute the update-task. here is the ant-part:



<updateDatabase
changeLogFile="${dev-db.changelog.file}"
driver="${database.driver}"
url="${dev.database.url}"
username="${dev.database.username}"
password="${dev.database.password}"
 promptOnNonLocalDatabase="${prompt.user.if.not.local.database}"

 dropFirst=“false”
classpathref=“build.lib.classpath”

/>

Hi,


is it possible that liquibase does not support changesets, that only hold a primary key? in our application we have a list of id’s for a department. we only need this id, no metadata attached. now my config looks like this:


  1.       
  1.             

  2.      </loadUpdateData

and the csv holding the data:

ID
"DUMMY_OID_GUT"
“DUMMY_OID_LIB”
“DUMMY_OID_STUD”


now when i execute an update, i get a misterious:

Reason: java.lang.StringIndexOutOfBoundsException: String index out of range: -1:
Caused By: String index out of range: -1


when i add a dummy-column, everything works fine… also liquibase with debug log-level doesnt give me any hint what could be wrong. is this a general limitation when using liquibase?

I’m not able to replicate it with the 2.0.4 codebase. I’m going to release that today or tomorrow. Could you test it out with that?

Nathan