A new topic, 'Max length for executeCommand arg value.', has been made on a
board you are watching.
You can see it at
http://liquibase.org/forum/index.php?topic=37.new#new
The text of the topic is shown below:
I'm trying to use the executeCommand statement. I'm noticing that if the value
in the arg statement is over about 32 characters, then liquibase locks up while
executing. I first noticed this behavior using 1.8.0, but confirmed that its
occurring in 1.9.3.
To help troubleshoot. I'm hitting a batch file that will echo out the
parameters passed in.
Here's the line from the command window
Jun 3, 2009 4:17:28 PM liquibase.database.template.JdbcTemplate comment
INFO: Lock Database
Jun 3, 2009 4:17:28 PM liquibase.lock.LockHandler acquireLock
INFO: Successfully acquired change log lock
Jun 3, 2009 4:17:29 PM liquibase.database.AbstractDatabase getRanChangeSetList
INFO: Reading from [DATABASECHANGELOG]
Jun 3, 2009 4:17:30 PM liquibase.database.template.JdbcTemplate comment
INFO: ChangesetXXX.xml::100::username::(MD5Sum: 1234567890abcef1234567890abcdef)
The output just stops there.
I'm running Java version 1.6.0_11. Has anyone else seen similar behavior?
Thanks
-- Erin
Unsubscribe to new topics from this board by clicking here:
http://liquibase.org/forum/index.php?action=notifyboard;board=1.0
Regards,
The LiquiBase Community Forum Team.
------------------------------------------------------------------------------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises
looking to deploy the next generation of Solaris that includes the latest
innovations from Sun and the OpenSource community. Download a copy and
enjoy capabilities such as Networking, Storage and Virtualization.
Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________
Liquibase-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/liquibase-user
