Jeremy, Seems you're right on this one. Postgres seems to use the DROP CONSTRAINT syntax while MySQL uses DROP FOREIGN KEY. An easy fix for this in my case would be to run a raw query using a drop foreign key, catch any errors and run a drop constraint in case of an error. If an error still pops up I'll just show it. This however isn't the nicest way of doing it. I'll take a look at the MySQL driver (as a start) and see if I can add a method drop_foreign_key. Thanks for the help!
Yorick -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sequel-talk?hl=en.
