On 8/30/06, JP <[EMAIL PROTECTED]> wrote: > > This is great news! > > One question comes to mind first, because I am nothing if not > self-absorbed. :) I wonder how much of the multi-db branch I have been > working on will be made irrelevant by this. Any thoughts on how the > sqlalchemy backend might support connecting different models to > different engines? I'd be more than happy to suggest parts of multi-db > to steal or adapt, or help with the stealing and adapting, if you're > planning to include something like per-model engines in the > implementation.
SQLAlchemy already has a DynamicMetaData object that can connect model objects to different database engines; I currently plan to use that. I'll definitely take a look at the multi-db code and would welcome any help you might want to offer. Whether the multi-db branch becomes irrelevant or not will entirely depend on adoption, I think. Maybe most people won't want to use the SQLAlchemy branch, and it will wither and die from lack of interest, while the multi-db branch will be widely used. Or maybe people will jump on the SQLAlchemy branch like it's the best thing since sliced bread, and it will become the default. It's far too early to tell. Basically, don't stop work on multi-db just because I'm starting this branch. I might hit a brick wall and not be able to complete it, or I might get hit by a bus tomorrow, or whatever -- you never know what's going to happen. I'd welcome any ideas or code you'd like to share, though. > More questions: Are you planning on building something like > ActiveMapper, or using ActiveMapper, or rolling up a whole new ORM > layer on top of the sqlalchemy core? If the last, I have some > play-around code (from sqlalchemy around 0.1, though) that I will > happily donate in case there is anything stealable or adaptable or > so-horrifying-you-know-never-to-repeat-it in there. Right now, I plan to use ActiveMapper -- why re-invent the wheel? I'd be happy to look at your code, though. I like "borrowing" from other people's work whenever I can, it means less work for me. :-) And that's what open-source development is all about, isn't it? -- Robin Munn [EMAIL PROTECTED] GPG key 0xD6497014 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
