OK, so what's not working?
On Fri, Feb 16, 2018 at 10:55 AM, wrote:
> Yes session.is_active is True.
> I really sure, because i log this operation.
>
> пятница, 16 февраля 2018 г., 13:50:51 UTC+3 пользователь Simon King написал:
>>
>> You haven't explained in what way it's not working with your
Yes session.is_active is True.
I really sure, because i log this operation.
пятница, 16 февраля 2018 г., 13:50:51 UTC+3 пользователь Simon King написал:
>
> You haven't explained in what way it's not working with your latest
> iteration.
>
> The last code you posted only called session.close() i
You haven't explained in what way it's not working with your latest iteration.
The last code you posted only called session.close() if
session.is_active was true. Are you sure you really are closing the
session?
Simon
On Fri, Feb 16, 2018 at 10:02 AM, wrote:
> This option does not suit me.
> M
Maybe you try to change same rows within several concurrent requests? I do
not use mssql, but in postgres it is normal.
Anyway it is normal behavior. One transaction tries to change a row,
another one tries to change the same. When the first transaction commited,
the second can continue its job.
п
This option does not suit me.
My app based on CherryPy 3.2.2.
I add more logging, and all session closing by
session.close()
in finally section.
I can't understand why this not work...
четверг, 15 февраля 2018 г., 18:07:49 UTC+3 пользователь Антонио Антуан
написал:
>
> You need just that:
> from