[sqlalchemy] Re: many-to-many orm warnings

2022-03-09 Thread Michael Merickel
Sorry for the rambling, it's been difficult for me to figure out what question to ask because I'm so confused. Below is the minimum viable example that produces no warnings with respect to the overlaps flags and I cannot explain hardly any of them. For example, why does Child.parents require "child

[sqlalchemy] Re: many-to-many orm warnings

2022-03-09 Thread Michael Merickel
I think ultimately I want the overlaps config but reading through https://docs.sqlalchemy.org/en/14/errors.html#relationship-x-will-copy-column-q-to-column-p-which-conflicts-with-relationship-s-y it doesn't make any sense to me what the values in the overlaps= argument are referring to. For example

[sqlalchemy] Re: many-to-many orm warnings

2022-03-09 Thread Michael Merickel
It's probably worth noting I can narrow it down to a single warning with the following snippet and it's still unclear to me how to resolve this: class Association(Base): __tablename__ = 'association' left_id = Column(ForeignKey('left.id'), primary_key=True) right_id = Column(ForeignKey

[sqlalchemy] many-to-many orm warnings

2022-03-09 Thread Michael Merickel
I have looked at the couple examples in the docs (many-to-many, and association table) and have noticed that my codebase has a slightly different pattern which is causing warnings when upgrading to 1.4. I'm trying to figure out the best pattern to accomplish what I've been doing which doesn't match