Maybe hold off on it for a few weeks to see if anything else ends up going in... but yeah.
On Feb 25, 2009, at 9:45 AM, Matt Aimonetti wrote: > Is it worth pushing a new release? > > - Matt > > On Wed, Feb 25, 2009 at 9:24 AM, Pavel Kunc <[email protected]> > wrote: > > Hi Lori, thanks a lot. > > Pavel > > On Feb 24, 11:57 pm, Lori <[email protected]> wrote: > > Pushed your changes into wycats/merb-plugins. > > > > On Feb 17, 2:53 pm, Pavel Kunc <[email protected]> wrote: > > > > > 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 thehttp://github.com/pk/merb-plugins > > > > > I hit the biggest problem today when I tried to do migrations > and use > > > timestamped plugins forSequel. Because the rake task started > Merb,Sequelstarted 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 usingSequelso you can get connection > > > usingSequel::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 forSequelhalf 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 -~----------~----~----~----~------~----~------~--~---
