Egor Egorov wrote:
Bug filled: http://bugs.mysql.com/bug.php?id=5784
Thank you!
Nice, thanks to you too ;-)
regards,
- Markus
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Bug filled: http://bugs.mysql.com/bug.php?id=5784
Thank you!
--
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.net http://www.ensita.net/
__ ___ ___ __
/ |/ /_ __/ __/ __ \/ /Egor Egorov
/ /|_/ / // /\ \/ /_
Hi,
Egor Egorov wrote:
Can you create a test case? I.e. a .sql file which is supposed to drop the
table well but instead fails?
Nevermind my last post, I found the workaround to disable foregin_key_checks
during import; interesting.
Here is a small example:
set foreign_key_checks=0;
CREATE TABLE
Hi,
Egor Egorov wrote:
Can you create a test case? I.e. a .sql file which is supposed to drop the
table well but instead fails?
This will help us determine if it's a bug and fix if it is.
Thanks, this hit a pretty interesting nail for me: I can dump it, but I can't load
the dump into the datab
Can you create a test case? I.e. a .sql file which is supposed to drop the
table well but instead fails?
This will help us determine if it's a bug and fix if it is.
Thank you!
--
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.n
