yeah always send us the error message with these since otherwise we have to
replicate it , as this mapping looks entirely fine. it asks for a primaryjoin,
and additionally the id column, until 0.7.0 is released where this has been
fixed, is in terms of Node not Department so you have to
I'm still having trouble getting an adjacency list relationship to
work within a child class (Department class in this example), and am
hoping someone might offer some insight:
class Node(Base):
__tablename__ = 'node'
id = Column(Integer, primary_key=True)
name = Column(String(100))
Whenever I try to establish an adjacency list relationship within a
child class (Department -- Parent Department in this case) the orm
complains about foreign key columns present in both the parent and
child class, and won’t construct the mapping. Below is an example
illustrating the problem. I'd
