I tried that. The trouble is that you run your migrations somewhat outside of Merb's normal loading context. I don't know if there is a config file somewhere to put this code in or something to tell rake to use this option or what.
On Feb 16, 7:20 am, Xavier Lange <[email protected]> wrote: > I don't know about any Merb::Plugins.config[:sequel] type of > interface, but you can interact directly with Sequel once the code has > been loaded by Merb and before the classes in app/models have been > loaded. In config/init.rb I have added > "Sequel::Model.raise_on_save_failure = false" to change that behavior > of Sequel. You might be able to do the same with your configuration > change. > > Xavier > > On Feb 15, 11:07 pm, cult hero <[email protected]> wrote: > > > How do I set the default table type to InnoDB in MySQL as a default in > > Merb? (I've asked this to the Merb list as well, but DataMapper is > > what most of them are familiar with.) > > > The release notes for 2.10 give the following command: > > > Sequel::MySQL.default_engine = 'InnoDB' > > > However, as the app I am building is theoretically database > > independent I don't want to put them in my Migrations. Is there an > > option in like Merb::Plugins.config[:sequel] I can set? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
