For the record, oracle doesn't have transactional ddl either, so that
shouldn't really be the deciding factor or toyness.
Sent from my iPhone
On Dec 3, 2009, at 9:56 PM, "Guido Neitzer"<[email protected]>
wrote:
On 3. Dec. 2009, at 17:25 , Kieran Kelleher wrote:
[...]
What would I like that I think I might be missing?
- transactional structure changes (ie., create table and roll
back.) transactions in InnoDB only apply to table/record edits
themselves.
So that is probably what screwed my migration so badly and I was
correct with my recollection that schema changes in MySQL are not
transaction safe - which makes the standard generated migration
files useless as soon as you do single table inheritance. I messed
around long enough with it, to get it somewhat working (hand
optimizing the migration to make it work with MySQL), but I prefer
to use FrontBase or PostgreSQL where it just works out of the box.
Thanks, I still stay away from MySQL.
Guido _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/mschrag%40mdimension.com
This email sent to [email protected]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
