On 8/30/06, Robin Munn <[EMAIL PROTECTED]> wrote: > 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?
This is probably something I should submit a patch for in ActiveMapper itself, but the biggest problem with ActiveMapper is that you can't get at the primaryjoin and secondaryjoin attributes to do the more involved mapping. As a result, I normally just do assign_mapper throughout, as ActiveMapper and non-ActiveMapper models don't work well together. AM itself is like 200 lines of code on top of the SA core. ;] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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/django-developers -~----------~----~----~----~------~----~------~--~---
