Hi, the merb_sequel gem in merb-plugins is kind of not loved so much. I've added couple of rake tasks and merged pusewicz's (and probably others) work as well on the http://github.com/pk/merb-plugins
I hit the biggest problem today when I tried to do migrations and use timestamped plugins for Sequel. Because the rake task started Merb, Sequel started to load information from the DB about tables which in combination with plugins (calling model.columns.include? :xy) results in exception. I removed dependency on :merb_env or :merb_start from the whole merb_sequel because it's not simple needed and create :sequel_env which just connects to the DB using Sequel so you can get connection using Sequel::Model.db. It has two advantages: 1) migration works, 2) it's much much faster (if you do it often) because it doesn't load Merb again and again. If you'd have any comments or wishes for the merb_sequel let me know, it would be shame to let driver for Sequel half baked! Cheers Pavel Kunc --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" 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/merb?hl=en -~----------~----~----~----~------~----~------~--~---
