SmileyChris, At the moment, I'm using the class_prepared signal to gather all loaded models. Theoretically I could use this to attach an SA attribute.
Are there use cases out there where you'd want to use *both* the Django and SA ORM's side by side? To me it makes more sense to import one or the other depending on what you plan on doing. For instance all of my code will use just the SA models, but the admin will still use the Django models. Paul On 10/5/07, SmileyChris <[EMAIL PROTECTED]> wrote: > > > > On Oct 6, 5:24 am, "Paul Davis" <[EMAIL PROTECTED]> wrote: > > Ben, > > > > I contemplated something like this, but I assumed that field > > properties would clash. For instance, after the call to mapper(...) > > you would no longer have access to Django ORM fields with the > > Model.field syntax (as they would be replaced by SA's). > > Could you use the post_init signal to attach a LazySAModel object as > an SA (or something) property of all newly created Django models? > > > > > --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
