at this point the entity_name should get set after your custom
create_instance is called (at least thats in the trunk). init_attr
is not required, it pre-sets attributes on the object that are
otherwise auto-created later (but the autocreation step throws a
single AttributeError per attribute, which hits performance a little
bit).
On Jan 15, 2007, at 12:19 PM, King Simon-NFHD78 wrote:
Michael Bayer wrote:
you can still override create_instance() as well and try to spit
out subclasses that are otherwise not mapped.
This was something I looked at a while ago as well, and I wasn't sure
what the requirements on objects returned from create_instance
were. If
it is not overridden, the mapper calls _create_instance, which sets
_entity_name and calls attribute_manager.init_attr. How important are
these things to the rest of the library?
Simon
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---
