Re: [pylons-discuss] SQLAlchemy create_engine future argument

Thanks for confirming this and all the info and links. I really appreciate it. It’s a big help. Thank you too Theron for your help. I hadn’t quite made it that far in the docs yet, but I’ve had a chance to look at it again. Thank you both! > On Aug 13, 2021, at 1:14 PM, 'Jonathan Vanasco' via

Re: [pylons-discuss] SQLAlchemy create_engine future argument

> It looks like the `future` flag on Engine and the `future` flag on Session are two separate things. So you need to add `future=True` to either sessionmaker or the Session constructor. Confirming this. There is also a `future` on `Connection` objects, but that is inherited from `Engine`. Se

Re: [pylons-discuss] SQLAlchemy create_engine future argument

Thanks for your help. I really appreciate it. After looking at this some more, self.request.dbsession.future is always False regardless of what I've tested. However, I did find self.request.dbsession.bind._is_future. If I use the code below in __init__.py:main() before settings is passed to Co

Re: [pylons-discuss] SQLAlchemy create_engine future argument

It looks like the `future` flag on Engine and the `future` flag on Session are two separate things. So you need to add `future=True` to either sessionmaker or the Session constructor. — Theron > On Jul 27, 2021, at 7:50 AM, Nate J wrote: > > Hi List, > > How should I set the the future ar

[pylons-discuss] SQLAlchemy create_engine future argument

Hi List, How should I set the the future argument to True in the call to create_engine()? >From https://docs.sqlalchemy.org/en/14/tutorial/engine.html >: The Engine is created by using create_engine(), specifying the create_engine.future f