Re: [sqlalchemy] Do I need a composite Secondary join for my hierarchical models?

On Sunday, 26 November 2017 02:24:29 UTC, Mike Bayer wrote: > > If you wanted Widgets.themes.sections to refer to some kind of object > that had just one Content on it, you need a much more complicated > mapping; some kind of object called a ContentTheme and a > ContentSection, which relate

Re: [sqlalchemy] Do I need a composite Secondary join for my hierarchical models?

On Sat, Nov 25, 2017 at 9:41 AM, Stephan Hügel wrote: > I'm trying to model a series of hierarchical relationships: > > Widgets can have many Themes, which can be shared by many Widgets > Themes can have many Sections, which can be shared by many Themes: > > Widgets - n:m -

[sqlalchemy] Do I need a composite Secondary join for my hierarchical models?

I'm trying to model a series of hierarchical relationships: - Widgets can have many Themes, which can be shared by many Widgets - Themes can have many Sections, which can be shared by many Themes: Widgets - n:m - Themes - n:m - Sections I'd also like to define a Content table with a