Comments on: Rails 2.1 broke my mysql foreign keys! http://blog.smartlogicsolutions.com/2008/06/24/rails-21-broke-my-mysql-foreign-keys/ News and updates from the people at SmartLogic Solutions Thu, 04 Dec 2008 20:44:11 +0000 http://wordpress.org/?v=2.7-bleeding By: Nigel Sharp http://blog.smartlogicsolutions.com/2008/06/24/rails-21-broke-my-mysql-foreign-keys/#comment-397 Nigel Sharp Sun, 12 Oct 2008 09:23:17 +0000 http://blog.smartlogicsolutions.com/2008/06/24/rails-21-broke-my-mysql-foreign-keys/#comment-397 Thanks for your kind help, I will give that a go. I hadn't realized that the fix could be implemented in my app's code, rather than rails itself ! Thanks once again, Nigel Thanks for your kind help, I will give that a go. I hadn’t realized that the fix could be implemented in my app’s code, rather than rails itself !
Thanks once again,
Nigel

]]> By: John Trupiano http://blog.smartlogicsolutions.com/2008/06/24/rails-21-broke-my-mysql-foreign-keys/#comment-390 John Trupiano Sat, 11 Oct 2008 13:23:25 +0000 http://blog.smartlogicsolutions.com/2008/06/24/rails-21-broke-my-mysql-foreign-keys/#comment-390 Hey Nigel, I continue to use the monkey patch I included at the top and drop it into initializers/. It seems to be the cleanest and most modular. Furthermore, when the app is upgraded to 2.2, I simply need to remove that file. The patch directly to the source that I included at the end requires the least amount of code, but it would probably require you to fork that version of rails and maintain it (because you'll need that version of rails on any box that will be used to develop/test/run in production), which seems like overkill. -John Hey Nigel,

I continue to use the monkey patch I included at the top and drop it into initializers/. It seems to be the cleanest and most modular. Furthermore, when the app is upgraded to 2.2, I simply need to remove that file.

The patch directly to the source that I included at the end requires the least amount of code, but it would probably require you to fork that version of rails and maintain it (because you’ll need that version of rails on any box that will be used to develop/test/run in production), which seems like overkill.

-John

]]> By: Nigel Sharp http://blog.smartlogicsolutions.com/2008/06/24/rails-21-broke-my-mysql-foreign-keys/#comment-389 Nigel Sharp Sat, 11 Oct 2008 13:10:02 +0000 http://blog.smartlogicsolutions.com/2008/06/24/rails-21-broke-my-mysql-foreign-keys/#comment-389 Hi John, Is there a best practise workaround for this ? Unfortuneately I'm stuck with Rails 2.1. When I specify foreign keys as :integer, they're ending up as BIGINT(11) in MySQL, resulting in failure to save my models. Thanks for any help you can give ! Cheers, Nigel Hi John,
Is there a best practise workaround for this ? Unfortuneately I’m stuck with Rails 2.1. When I specify foreign keys as :integer, they’re ending up as BIGINT(11) in MySQL, resulting in failure to save my models. Thanks for any help you can give !
Cheers,
Nigel

]]>