(1) Never use MyISAM - no transactional support means a failed editingContext.saveChanges() will not result in a rollback and semi-saved changes to the database..... data integrity goes out the window. Use InnoDB .... don't just convert live DB though, dump/import to a standby server, configure InnoDB first completely and actually do a little bit of studying the MySQL docs to understand how. Also, get a head start here: https://github.com/kierankelleher/gic-mysql-tools
(2) Don't create "real" foreign key constraints because MySQL does not support deferred constraints (which is the biggest negative of using MySQL). Instead just manually create indexes on every foreign key field. Otherwise your performance will deteriorate as tables sizes get larger.
On Apr 13, 2012, at 8:20 AM, Ron X wrote: sorry, we check - we used MyISAM - and it has not transactions and foreign keys
13 апреля 2012 г. 15:09 пользователь Pascal Robert <email@hidden> написал:
Le 2012-04-13 à 07:50, Ron X a écrit :
> hi community
>
> does EOF use foreign keys?
>
> we use in Migration java class:
>
> ERXMigrationTable oldCodeTable = database.newTableNamed("Code");
>
> oldCodeTable.addForeignKey("repTypeId", "rep_type", "_rowid");
> oldCodeTable.addForeignKey("actionId", "action", "_rowid");
>
> but no foreign keys created.
>
> we scanned our 40G db and find NO foreign keys in it
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
|