How to publish changes

[expired user #4769]'s profile image [expired user #4769] posted 14 years ago in General Permalink
Hi guys,

I have had encounter a problem with the export function, when using InnoDB tables with foreign keys. The original function does not take care for the order of the exported (and later imported) tables. So it was not possible to export and import a database.

For this reason I downloaded the source code and developed a workaround, by extracting all foreign key constraints from the original create statement and put them behind the table creations (with an alter table statement).

It is working fine now and I want to publish my changes. I can not use svn, because I have no account (at least I can not remember having one).
So, how do I publish in a proper way?

Thanks in advance
ansgar's profile image ansgar posted 14 years ago Permalink
Feel free to send a SVN diff/patch. Paste it here if it's small enough or send it by mail.

Of course there is no public write access to the SVN as I want to keep an eye on the committed changes.
[expired user #4769]'s profile image [expired user #4769] posted 14 years ago Permalink
It is too many small changes to post it here.

To which mail address should I send it?
ansgar's profile image ansgar posted 14 years ago Permalink
Glad I found Heidi has already a fix for that: In any SQL export, this conditional comments suspends foreign key checks until the script has finished:

/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;


At the end of the script that is enabled again (if it was enabled before):

/*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */;


No need to do it more complicated.
[expired user #4769]'s profile image [expired user #4769] posted 14 years ago Permalink
Mh, my export also did not show this problem again - sry for making trouble.
But another problem occured: syntax (t)error in trigger creation. This is due to missing delimiter change before trigger create statement.
ansgar's profile image ansgar posted 14 years ago Permalink
That sounds like you're using an old revision? Please look at issue #1672 and r3063.

Please login to leave a reply, or register at first.