Tamir Duberstein
Tamir Duberstein
That's a sharp edge to say the least. I think it would be great to document this on every single affected method. See e.g. [any](https://docs.sqlalchemy.org/en/20/orm/extensions/associationproxy.html#sqlalchemy.ext.associationproxy.AssociationProxyInstance.any).
The situation is even worse if you filter by the computed column. Adding ```python for user in await session.scalars(select(User).where(User.data == "one")): print(user) for user in await session.scalars(select(user_prime).where(user_prime.data == "one")): print(user)...
> that is, there's no guesswork SQLAlchemy can be doing here that omits it from some places where you then might need it to be present. if you removed it...
They both refer to the same object, right? Shouldn't the ORM detect this somewhere and generate a reference instead of repeating the expression? Maybe that's not how the ORM works.
Ah, i see - but you could if that expression was in the CTE. ```sql with cte as ( select id, 'hello' as c from public.user ) select * from...
Oops, sorry about the CI failures, I had neglected to update the Github Actions config. Could you give it another go?
Alright, this should be green for real now. I worked out the kinks by running CI in my fork.
@mystor does this look reasonable to you?
@mystor gentle ping.
Please let me know if changes are required - or go ahead and make what changes you see fit. I've allowed edits by maintainers and you have my explicit consent...