On Tue, Jan 5, 2021, at 9:50 AM, kz...@us.ibm.com wrote:
> Thanks mike!
>
> I understand that it should work when querying over SQLAlchemy API. the
> missing part of my use case I forgot to provide is, it only uses
> Alembic/SQLAlchemy to manage schema changes, while the actual query may
Thanks mike!
I understand that it should work when querying over SQLAlchemy API. the
missing part of my use case I forgot to provide is, it only uses
Alembic/SQLAlchemy to manage schema changes, while the actual query may
comes from other query engine like a dashboard, a desktop DB client or a
This is the casing convention of the database and SQLAlchemy does not consider
the name to be in "uppercase" or "lowercase" (or even "mixed case") but rather
"case insensitive", which really means the name is referred towards without any
quoting.When no quoting is applied, there is
The use case is migrating data from a Db2 instance (where schema is not
managed under Alembic migration) to a postgresql instance (where I plan
to manage schema via Alembic).
In Db2, by default, it stores unquoted mixed case identifiers in
Uppercase. While the postgres I got it stores unquoted
