On May 23, 2008, at 2:49 AM, schickb wrote:
>
> On May 22, 8:37 pm, schickb <[EMAIL PROTECTED]> wrote:
>> Maybe SA is putting second execute in a transaction that isn't
>> being commited?
>
> That was the problem. I found this in the SA docs: "While many DBAPIs
> implement a flag called autocomm
On May 22, 8:37 pm, schickb <[EMAIL PROTECTED]> wrote:
> Maybe SA is putting second execute in a transaction that isn't
> being commited?
That was the problem. I found this in the SA docs: "While many DBAPIs
implement a flag called autocommit, the current SQLAlchemy behavior is
such that it imple
