databases
databases copied to clipboard
Backends crash when the user selects duplicate columns
This is to mirror the upstream issue in SQLAlchemy 1.4. Those folks happily discarded our problem because we were using the private API at first, but later showed a humane attitude and advised on changing to the new public API that appeared in 1.4. As if we had a choice in 1.3. Somebody has to study the new 1.4 code and update the backends' column mappings to support selecting duplicate columns.
Wouldn't that affect all backends? They basically use the same attribute.
And I don't think the description is really accurate, maybe you might want to update that.
~~It doesn't affect at least the asyncpg backend. I am not changing the description, sorry.~~ :facepalm: It doesn't affect asyncpg backend in my company's fork. Indeed, I see that the issue is global upstream.