On Oct 10, 2009, at 1:35 PM, Faheem Mitha wrote:
>
> On Fri, 9 Oct 2009 22:34:11 -0400, Michael Bayer
> wrote:
>
>>
>> On Oct 9, 2009, at 7:35 PM, Faheem Mitha wrote:
>>
>>> Can you explain why removing the "SET search_path TO public;" string
>>> makes a commit happen? You also say "that string
On Fri, 9 Oct 2009 22:34:11 -0400, Michael Bayer
wrote:
>
> On Oct 9, 2009, at 7:35 PM, Faheem Mitha wrote:
>
>> Can you explain why removing the "SET search_path TO public;" string
>> makes a commit happen? You also say "that string you have will not
>> trip off SQLA's "autocommit" feature." Ho
On Oct 9, 2009, at 7:35 PM, Faheem Mitha wrote:
> Can you explain why removing the "SET search_path TO public;" string
> makes a commit happen? You also say "that string you have will not
> trip off SQLA's "autocommit" feature." How does this autocommit
> feature work, and are there certain stri
[This message has also been posted.]
On Fri, 9 Oct 2009 13:28:58 -0400, Michael Bayer
wrote:
> did you commit your transaction or set autocommit=True in your text()
> statement ? that string you have will not trip off SQLA's "autocommit"
> feature.
Hi,
Thanks for the explanation. No, the co
did you commit your transaction or set autocommit=True in your text()
statement ? that string you have will not trip off SQLA's "autocommit"
feature.
Faheem Mitha wrote:
>
> Confirmed by Alex Grönholm on #postgresql on freenode with pg 8.3 and sqla
> 0.5.6. If this is not a bug, i'd like to kn
Confirmed by Alex Grönholm on #postgresql on freenode with pg 8.3 and sqla
0.5.6. If this is not a bug, i'd like to know what is going on. Typing the
text in gq directly into psql (all on one line) produces the schema foo as
expected.
