On Thu, Feb 27, 2020, at 1:39 PM, doi zece wrote:
> Yes I want to see the SQLs hitting the DB. The initial issue I've mentioned
> got resolved. What I'm trying now is to generate more logs, so that it will
> be easier for me to investigate future similar issues.
>
> When you say "SQL logging w
On Thu, Feb 27, 2020, at 2:49 PM, Ke Zhu - k...@us.ibm.com wrote:
> On Wed, 2020-02-26 at 11:07 -0500, Mike Bayer wrote:
>> oh, that issue is talking about rowcount. Alembic does not need rowcount to
>> function correctly. I see that Alembic is doing this now, however there is a
>> dialect-leve
On Wed, 2020-02-26 at 11:07 -0500, Mike Bayer wrote:
oh, that issue is talking about rowcount. Alembic does not need rowcount to
function correctly.I see that Alembic is doing this now, however there is a
dialect-level flag called "supports_sane_rowcount", if this were False, Alembic
should
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 resolved. What I'm trying
Yes I want to see the SQLs hitting the DB. The initial issue I've mentioned
got resolved. What I'm trying now is to generate more logs, so that it will
be easier for me to investigate future similar issues.
When you say "SQL logging will render all the SQL" you mean i have to
configure a new
SQL logging will render all the SQL being emitted which should be enough to see
everything the script is doing against the database. that is, if you ran
op.alter_column(), you'd see "ALTER COLUMN..." in the log. not sure what else
you are looking to see.
do you think you're having a deadlock in
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
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
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 no luck.
The only way that i manage to make it print someting in the console was to
add print statement in the script.
This is the current s
the --verbose flag is only used for a command like "alembic history" to provide
more detail. to see Alembic doing its work you want to enable logging. in the
ini file (see
https://alembic.sqlalchemy.org/en/latest/tutorial.html#editing-the-ini-file)
you want to set [logger_sqlalchemy] level to I
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
11 matches
Mail list logo
