Re: [sqlalchemy] Accessing association-specific data from a self-referential many-to-many relationship using association_proxy?

complicates things, since most resources I find have two distinct objects along with the association. On Monday, July 6, 2015 at 1:14:29 PM UTC-4, Michael Bayer wrote: On 7/6/15 12:06 PM, Ryan Holmes wrote: I have an interesting problem that I haven't been able to solve for quite

[sqlalchemy] Accessing association-specific data from a self-referential many-to-many relationship using association_proxy?

I have an interesting problem that I haven't been able to solve for quite some time. I keep finding information about association proxies and the like, but nothing that really helps (or maybe I'm implementing it incorrectly). Let's start with this: class HandledProjectedItemList(list):

[sqlalchemy] SQLlite: enforce a unique constraint on a relation?

(cross posted from https://stackoverflow.com/questions/49225846/) Lets say I have 3 tables: parent, child, and a linker table for the two for a many-to-many relationship, `parentChildren`. Each parent can have multiple children, and each child can have multiple parents. If parent 1 already has

Re: [sqlalchemy] SQLlite: enforce a unique constraint on a relation?

Thanks Mike, While I would rather this be a hard constraint on the database, not enforced in python, I understand that SQLite is pretty limited in this regard, so I'm down to try anything really. I also had the idea of using a custom collection simply because the project already uses them