the deprecation warning is from the SQLAlchemy side and we need to remove it
which will be for 1.4.
Also we've identified a bug in cx_Oracle in this area that's not fixed yet, a
cx_Oracle 2pc transaction cannot be replaced by a non-2pc transaction on a
single connection:
Hi Mike,
I'm effectively using cx-Oracle... but I didn't notice any deprecation
warning! Maybe it's because I'm still using release 8.0.1 (as I still need
Python 3.5 support)?
If you need anyone to test for cx-Oracle features, just ask!
Anyway, I'm also using other "no-transactional" databases
FWIW, within the realm of pyramid_tm, the more common use-cases for
two-phase transaction support are for sending mail and a dealing with task
queues - not two separate databases.
On Wednesday, January 27, 2021 at 2:40:21 PM UTC-5 Mike Bayer wrote:
>
>
> On Wed, Jan 27, 2021, at 2:23 PM,
On Wed, Jan 27, 2021, at 2:23 PM, Thierry Florac wrote:
> Hi,
> I'm actually using two databases connections: one is my "main" connection,
> opened on a ZODB (with RelStorage), and **sometimes** I have to open another
> connection on another database (and event more sometimes); the two
>
Hi,
I'm actually using two databases connections: one is my "main" connection,
opened on a ZODB (with RelStorage), and **sometimes** I have to open
another connection on another database (and event more sometimes); the two
transactions have to be synchronized: if one of them is aborted for any
On Wed, Jan 27, 2021, at 8:32 AM, Thierry Florac wrote:
>
> Hi,
> I'm actually using SQLAlchemy with Pyramid and zope.sqlalchemy packages.
> My main database connection is a ZODB connection and, when required, I create
> an SQLAlchemy session which is joined to main transaction using this kind
Hi,
I'm actually using SQLAlchemy with Pyramid and zope.sqlalchemy packages.
My main database connection is a ZODB connection and, when required, I
create an SQLAlchemy session which is joined to main transaction using this
kind of code:
from sqlalchemy.orm import scoped_session, sessionmaker
