- changed status to wontfix
implement polymorphic get()-like behavior for concrete inheritance
Issue #678
resolved
currently, get() from the base mapper in concrete inheritance needs to issue a query in all cases; instance keys still use the actual class in their tuple so get() from the base mapper can never identify the object by instance key.
a composite-PK approach needs to be built into concrete such that the polymophic_on column is added to their PK; but also such that get() on query adds this value in automatically when its known.
Comments (2)
-
reporter -
reporter - removed milestone
Removing milestone: 0.4.xx (automated comment)
- Log in to comment
this ticket makes no sense at all. what does :
return ? id
#5could be in any or all of each concrete table. thats just a fact of how this works - with concrete you need to know the type. explicitly putting the polymorphic identity in theget()
pk argument is redundant vs. just specifying theQuery
against the correct subtype.