And nope. It's coming when I'm running `aliased`, but it doesn't seem to be directly related, even though it's the same warning. I think it has to do with how I'm translating inherited models. Sorry for the false alarm.
On Wednesday, May 19, 2021 at 8:50:56 PM UTC-5 Ryan Hiebert wrote: > So I am able to just add it on the many-to-many relationship, that worked > just fine. Unfortunately, I'm now having a similar issue come up when I use > `aliased` on a generated model. Do you have any suggestion for how to > handle that? It strikes me that either (a) aliased doesn't expect to be > working with models with relationships, or (b) aliased really shouldn't be > causing this warning, because of course it will be duplicating > relationships, right? -- SQLAlchemy - The Python SQL Toolkit and Object Relational Mapper http://www.sqlalchemy.org/ To post example code, please provide an MCVE: Minimal, Complete, and Verifiable Example. See http://stackoverflow.com/help/mcve for a full description. --- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sqlalchemy/9fec53bf-e160-4970-a616-b1a669db7074n%40googlegroups.com.
