Hi folks,
Making some headway on setting up in-memory, test databases, but I've
encountered a "type" problem. We currently define a couple of columns
as the type LONGTEXT, because we anticipate storing really large strings
of data. If I understood my reading of the Liquibase docs, it is
pref
A couple options:
- You could create a subclass of the MySqlDatabase class and override
the getClobType() method. You can pass the databaseClassName into
liquibase.
- You could also specify the type as a parameter: and then pass the value into liquibase.
I would think that either option would be
Cool. Thanks, Nathan.
Voxland, Nathan wrote:
> A couple options:
> - You could create a subclass of the MySqlDatabase class and override
> the getClobType() method. You can pass the databaseClassName into
> liquibase.
> - You could also specify the type as a parameter: type="${clobType}"/> and t
It's me again! :-)
I've got my changelog.xml modified to handle my test vs. production
environment issues, but I have another associated problem, now. My
testing class calls the Liquibase API to build an in-memory database,
but it is executing the wrong contexts. I added the contexts, as a
There is an attribute or element you can add to changeSets for putting
in "other" valid checksums. You put the old changeSet checksum in there
that the production system has already, then make your edit to the
changeSet. Now all future checks use a new checksum and the current
production sys
Thanks for the tip, Ben. That might be very helpful to me.
I found a tid-bit in the docs, too, that helped me solve my other problem.
Ben Wolfe wrote:
> There is an attribute or element you can add to changeSets for putting
> in "other" valid checksums. You put the old changeSet checksum in th
Yes, the tag to use is .
Also, the MD5sum is computed on the final XML after any parameters are
put in, so if you originally executed a changeset as:
And changed it to:
But passed in "lon
Hey Nathan. Yeah, not needing the "all" context was the tid-bit that I
stumbled upon. I had not realized until then that I could put a
comma-separated list in my changelog.xml. Once I changed that, it was
working just fine.
I still ended up hitting a roadblock, because something about HSQLDB
d
What is the stacktrace?
Seeing issues people have also helps me know uses and places of
confusion. Thanks for your questions.
Nathan
On Mar 16, 2009, at 4:28 PM, "David C. Hicks"
wrote:
> Hey Nathan. Yeah, not needing the "all" context was the tid-bit that I
> stumbled upon. I had not re
I'm afraid I didn't keep a copy of it, but it amounted to a problem
within Hibernate/JPA where the autoincrement ID of one of my objects
could not be read back after the object was persisted. This was long
after the call to Liquibase had completed and the test case was into the
setUpInTransact
No if it's not a liquibase problem I don't care as much :)
Welcome to the wonderful world of database differences...
Nathan
On Mar 16, 2009, at 6:37 PM, "David C. Hicks"
wrote:
> I'm afraid I didn't keep a copy of it, but it amounted to a problem
> within Hibernate/JPA where the autoincrem
11 matches
Mail list logo
