I think that there might be an even bigger opportunity here; with three different ORMs in play, it's going to make it more complicated to specify models (or generate migrations) in plugins. Hobofields could probably be set up as the abstraction layer, that works with *any* of the ORMs to generate migrations and wrap field data.
Otherwise, I would think that there'd be some fracturing within the community; most plugin authors aren't going to want to support a whole stack of adapters, and running more than one would seem to be bad for performance.. --Matt On Dec 24, 2008, at 6:32 AM, James Garlick wrote: > > At the moment Hobo has the same issues with modularity that Rails has, > in that it makes it quite hard if you want to use alternatives. I'm > hoping that as Rails becomes more modular it will force Hobo to do the > same. For example Hobo Fields is essentially an extension to Active > Record, but it should be possible to use all of Hobo apart from the > Active Record extensions with another ORM like DataMapper. > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hobo Users" 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/hobousers?hl=en -~----------~----~----~----~------~----~------~--~---
