Dave
How are you setting InnoDB as the default? Is there a way apart from
appending this to the connection string:
"&sessionVariables=storage_engine=InnoDB" ?
Ben
David C. Hicks wrote:
> False alarm. Sorry.
> I discovered that on the databases that were missing foreign keys we had
> failed
I agree, there are always more features to write. Extras like this
always get bumped by developers because they know the xml config so well.
We recently incorporated liquibase into openmrs and the other developers
are asking (whining) for an eclipse plugin. However, because I did the
integr
Yes, there is a way. With the ant task you can set diffTypes="data" to
just give you the rows in the generated xml. I'm not sure what the
argument is for the jar file though. I can't find that in my command
history or in the jar help text.
Ben
Pradnya Gawade wrote:
> Hi,
>
> I am new to li
I would prefer there be a way to turn it off as well. There have been
several times where the database wasn't unlocked because tomcat crashed
at just the wrong time in liquibase's startup.
Ben
Voxland, Nathan wrote:
> Is that a feature others would like?
>
> My assumption has been that it do
trunk/core/.classpath references these files but they aren't in /lib:
Is there a reason you're not committing these Nathan?
Also, MD5UtilTest can't seem to find the import
"hidden.org.codehaus.plexus.util.StringInputStream". Taking out that
line and just using a normal string the te
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
You could just set your jdbc connection string to use InnoDB as the
default storage engine (requires java connector > 5.1)
jdbc:mysql://localhost:3306/databasename?autoReconnect=true&sessionVariables=storage_engine=InnoDB
Ben
Voxland, Nathan wrote:
> That does work well if you are not wanting
tabasechangelog instead of our database_version. I don't know
what this looks like in other databases, but it probably is similar.
update-to-latest.sql:
#
# OpenMRS Datamodel version 1.1.10
# Ben Wolfe May 31st 2007
# Adding township_
y
then I'll help make it and review it. I just don't think it can be
done without repeating 80% of what Liquibase does in Database specific
procedures, and that is a solution I don't think is worth building.
Paul
--
We create the database with the default set to utf8 and then don't have
to specify the character set when creating tables:
create database xxx default character set utf8;
Ben
Sven Haiges wrote:
> I am experimenting to create an empty table, then use manual sql to
> change the default charset
I made a few that you can find here:
http://dev.openmrs.org/browser/openmrs/trunk/src/api/org/openmrs/util/databasechange
The liquibase changelog that uses them is here:
http://dev.openmrs.org/browser/openmrs/trunk/metadata/model/liquibase-update-to-latest.xml
Ben
On Tue, 2009-06-23 at 15:54 -0
11 matches
Mail list logo
