Yes it surprised me. But I get your point.
Thanks you for your response.
On Nov 26, 9:41 pm, Michael Bayer mike...@zzzcomputing.com wrote:
I wouldn't say its a bug since its intentional. But I'll grant the
intention is up for debate. I've always considered usage of execute() to
mean,
I might turn it on in 0.7 and add an extra flag autoflush_on_execute just so
people can turn it off if they don't like it. 0.7 is on track for beta
releases in december or january.
You can make yourself a quick Session subclass that wraps execute(), if you
wanted this behavior right now.
