Can you send complete stack trace please? That's the main thing that will
show which query this is occurring on (there are several upon connect).
Also full detail on SQL server version, odbc driver, client operating
system.
On Jul 3, 2017 7:26 PM, "Paul Morel"
Hi,
I have been trying to diagnose this issue in a Windows Python 2.7 (Anaconda
installed) environment running SQLAlchemy=1.1.11, pyodbc=4.0.17, and
pymssql=2.1.3.
Both pyodbc and pymssql connections will successfully connect and query a
table correctly. However, when I attempt the same
On Mon, Jul 3, 2017 at 7:57 AM, David Moore wrote:
> I understand this is done for performance reasons, and in the very common
> case that all you want from your Sequence is to autogenerate a unique id,
> it's absolutely fine. However, it would be nice to have an option to
>
Hello,
I just chased down a bug in our application while using SQLAlchemy 1.0.6 in
an Oracle RAC environment, which should probably be in SQLAlchemy
documentation somewhere, and possibly motivate a change to the options for
sequence creation on Oracle.
Basically, our application assumes a