[Cosmo-dev] mysql migration script checked in

[Jared Rhine]

Randy Letness wrote:
> The  problem I ran into was that I had some tables in MyISAM, and some 
> tables in InnoDB and the script choked when trying to create a foreign 
> key constraint between a MyISAM and InnoDB table.

That makes sense.

> On a 
> new installation, we really on Hibernate's auto schema generation, which 
> does not support setting the table type.

Blech, ok.  I might argue that we should leave everything as is, as 
people might want to pick their storage engine, but given there's only 
one engine which supports all requirements (5.x+, txns, FKs), only 
InnoDB suits currently.  Given that the admin just needs to be careful 
here, I guess leaving as-is is still the best plan.

> That's the reason you need to 
> set the default for the database (not the server as a whole) to InnoDB.

Do you know how to do this (server the default engine for a specific 
database)?  I didn't know this was possible and can't find documentation.

>> People who install 0.6.0 will get that as a 
>> version, 0.6.1 will get that, even though the schema is likely to be 
>> identical.
> 
> For the proposed 0.6.1 sharing release, there probably will be changes.

Ok.  I'd normally say schema changes should be confined to dot-releases, 
but I understand our upcoming situation.  Where do you stand on ordinal 
db versions versus use of Cosmo versions?

>> What are the most likely areas where bugs might arise?
> 
> Most likely in minor schema differences (length of fields, correct 
> indexes, constraints, etc.).

Length of fields we could maybe check via test plans.  Constraints seem 
harder.  Not sure how to test indexes either.

-- Jared