Skip Menu |
 

This queue is for tickets about the SQL-Translator CPAN distribution.

Report information
The Basics
Id: 70354
Status: open
Priority: 0/
Queue: SQL-Translator

People
Owner: Nobody in particular
Requestors: TILLY [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Upgrading enum to foreign key can cause error
Download (untitled) / with headers
text/plain 491b
If you have two tables, and then change an enum in the first to a foreign key in the second, the reasonable SQL you get from SQL::Translator triggers error 150 from inside of MySQL. If the second table did not exist at the start, the error goes away. I suspect a MySQL bug. See https://gist.github.com/1152817 for a script that translates between 2 SQL statements that demonstrates the error. If I load the dest SQL into my database, then apply the diff SQL, I get the reported error.
Download (untitled) / with headers
text/plain 823b
On Thu Aug 18 17:42:50 2011, TILLY wrote: Show quoted text
> If you have two tables, and then change an enum in the first to a > foreign key in the second, the > reasonable SQL you get from SQL::Translator triggers error 150 from > inside of MySQL. > > If the second table did not exist at the start, the error goes away. > > I suspect a MySQL bug. > > See https://gist.github.com/1152817 for a script that translates > between 2 SQL statements that > demonstrates the error. If I load the dest SQL into my database, then > apply the diff SQL, I get > the reported error.
We really do want to eventually fix this bug, but currently the sqlt dev-process is quite udnerstaffed. Can you help us out by converting the gist into a proper failing test case, modeled on other existing .t's? This will make things sooo much easier :) Cheers!


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.