Re: [sqlalchemy] Abstract Table Concrete Inheritance. Could not determine join condition between parent/child tables

2017-05-16 Thread mike bayer
On 05/15/2017 09:27 PM, Никита Крокош wrote: So, how should i do if I need many encumbrances for every cadastral object (flat.encumrances, building.encumbrances, ...etc). If I get it correctly, I need something like: class iCadastralObject(Base): __abstract__ =True def

Re: [sqlalchemy] Abstract Table Concrete Inheritance. Could not determine join condition between parent/child tables

2017-05-15 Thread Никита Крокош
So, how should i do if I need many encumbrances for every cadastral object (flat.encumrances, building.encumbrances, ...etc). If I get it correctly, I need something like: class iCadastralObject(Base): __abstract__ = True def __init__(self, cadastral_region, cadastral_district,

Re: [sqlalchemy] Abstract Table Concrete Inheritance. Could not determine join condition between parent/child tables

2017-05-15 Thread mike bayer
when you use concrete inheritance, you now have three tables: building, flat, construction. If you'd like these to each have a relationship to iencumbrance, that's three separate foreign key constraints. Given the four-column primary key, you'd need to have twelve columns total on

[sqlalchemy] Abstract Table Concrete Inheritance. Could not determine join condition between parent/child tables

2017-05-15 Thread Никита Крокош
This is a duplicate from: http://stackoverflow.com/questions/43972912/abstract-table-concrete-inheritance-could-not-determine-join-condition-between I've got following example code: models.py class CadastralObject(Base): __tablename__ = 'cadastral_object' def __init__(self,