Yes. I tried adding the autocommit execution option and calling execute, as
well as turning autocommit off and manually calling commit.
Like I said, the stored procedure is getting run because the primary key is
incrementing internally, (that is to say, that if my last id entry was 1, I
run
Do you have echo=True on and do you see the COMMIT logging lines that you
expect to see ? if so, does it work with a raw DBAPI script that sends out the
necessary SQL ? otherwise it sounds like the procedure itself is broken.
I dont see how the concept of primary key incrementing impacts
Hello all!
I'm having this *exact* bug from a few years ago wrt. calling stored
procedures.
https://groups.google.com/forum/?fromgroups#!topic/sqlalchemy/qA_ypVgJ1B0
What makes it worse, however, is that adding the autocommit execution
option or explicitly starting and stopping a transaction
did you call Session.commit() ? otherwise you're still in an open transaction,
assuming default settings.
Session.execute() is not the same as engine.execute(), where the latter is
autocommitting (assuming you also called execution_options(autocommit=True) for
this particular text()
