Thank you Michael, I will use subclassing instead.
A mention of this technique in the documentation (in the Multiple
Mappers for One Class) would be great, as it is the place I was
looking for a solution to my problem when I found entity_name.
Best regards,
Christophe
2008/7/7 Michael Bayer
It's currently preferred if you didn't use entity_name since it works
quite poorly and even worse in 0.5, and we'd like to remove it - it
has built-in undefined behavior in that its not determined which set
of attribute instrumentation gets applied to the class.
This feature is an artifact
On Monday 07 July 2008 18:10:19 Michael Bayer wrote:
It's currently preferred if you didn't use entity_name since it
works quite poorly and even worse in 0.5, and we'd like to remove
it - it has built-in undefined behavior in that its not determined
which set of attribute instrumentation gets