On Jul 28, 2008, at 5:21 AM, az...@svilendobrev.com wrote:
another one that comes to mind is concrete-table inheritance; it works
in simple cases and breaks in more complex ones. While using dbcook i
have invented some way of avoiding it, by having base-classes that
define attributes/relations but are not ORMapped
(DBCOOK_no_mapping=True) - but then the ORM has no idea of that
inheritance _at_all. the other way is "dont use", use
joined-table-inheriance.
do u have any plans for fixing that? i'm not really needing it - this
is for consistency.
concrete should always be improved as needed. unlike entity_name, it
is a real use case without any simpler substitute. i dont think
concrete's issues are as severe, either.
3 messages in com.googlegroups.sqlalchemy[sqlalchemy] Re: removing entity_name...