On 01/17/2017 06:15 AM, Chris Withers wrote:
Great, thanks. I assume has_inherited_table returns False where the
table is defined on the class itself?
it looks like has_inherited_table is just looking for non-None __table__
attribute up the inheritance chain.
(ie: normal models, and the "base" model in the case of single table
inheritance)
Chris
On 16/01/2017 17:49, mike bayer wrote:
at the declarative level we have this:
http://docs.sqlalchemy.org/en/latest/orm/extensions/declarative/api.html#sqlalchemy.ext.declarative.has_inherited_table
this might be better since you're really looking for a "table" up
above....
On 01/16/2017 12:05 PM, Chris Withers wrote:
Hi All,
If I'm using instrument_class events to add some constraints to a table,
what's the 'right' way to spot when it's a subclass is being
instrumented? (where I'm guessing I shouldn't add the constraints).
My current attempt is here:
https://github.com/Mortar/mortar_mixins/commit/b82bea1dbc1393e24116943804b192df056a70e7
...but that feels a bit hacky.
Thoughts?
Chris
--
SQLAlchemy -
The Python SQL Toolkit and Object Relational Mapper
http://www.sqlalchemy.org/
To post example code, please provide an MCVE: Minimal, Complete, and Verifiable
Example. See http://stackoverflow.com/help/mcve for a full description.
---
You received this message because you are subscribed to the Google Groups "sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sqlalchemy+unsubscr...@googlegroups.com.
To post to this group, send email to sqlalchemy@googlegroups.com.
Visit this group at https://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.