Oh, found my problem. The sqlalchemy log level was not set properly for me
to get the SQLs.
Thanks for your support.
On Thursday, February 27, 2020 at 1:39:00 PM UTC-5, doi zece wrote:
>
> Yes I want to see the SQLs hitting the DB. The initial issue I've
> mentioned got reso
hink you're having a deadlock in Python and not against the
> database? there's no good way to debug that without using something like
> pdb or embedding print statements. that's a very unusual kind of issue in
> a tool like alembic and there are no known issu
OK I managed to get some logging (it seems my alembic env.py was missing
the fileConfig(config.config_file_name)). But still I'm not getting what i
want.
Basically i want a long entry for every single operation in the migration
script. And this, if possible, without having to add log statements
d log statements all
over the place. Is that possible ?
On Thursday, February 27, 2020 at 12:54:56 PM UTC-5, doi zece wrote:
>
> I've tried that already but with no success. I also tried to change the
> alembic version (move to the latest one) as initially i was on a 0.8.x .
> Still n
EBUG. this will show
> you every SQL statement emitted which should give you an idea of the one
> that is hanging. DROP TABLE is a likely culprit as many databases won't
> allow this if there are open transactions accessing that table.
>
>
> On Thu, Feb 27, 2020, at
n one of the python projects I'm working on we are using alembic to handle
the DB migration scripts. Lately he had an incident when container ,in
which alembic upgrade head is running, got stucked ( by some locks on the
DB set the the runtime app) and eventually timed out without giving any
d
