> > On Feb 11, 9:10 am, Michael Bayer wrote:
> that is absolutely true.
>
> works in all of our tests do you have one to demonstrate ?
Thanks Michael, finally tracked this one down while creating tests
that weren't reproducing the issue.
It didn't dawn on me that the render() function in T
On Feb 11, 2011, at 2:55 PM, Romy wrote:
> On Feb 11, 9:10 am, Michael Bayer wrote:
>>> For instance, rearranging the below to:
>>
>>> user = User.query.filter_by(id=1).first()
>>> user.x = user.x + 1
>>> elixir.session.commit()
>>
>>> results in a BEGIN, SELECT, UPDATE, COMMIT log output. Whe
On Feb 11, 9:10 am, Michael Bayer wrote:
> > For instance, rearranging the below to:
>
> > user = User.query.filter_by(id=1).first()
> > user.x = user.x + 1
> > elixir.session.commit()
>
> > results in a BEGIN, SELECT, UPDATE, COMMIT log output. When I
> > introduce another query before the commit
On Feb 11, 2011, at 4:32 AM, Romy wrote:
> Fair enough, though it appears to be a little inconsistent and thus
> confusing, since I do see COMMIT statements in the log output.
we call connection.commit() and we log the phrase "COMMIT" in the output.
>
> For instance, rearranging the below to
Fair enough, though it appears to be a little inconsistent and thus
confusing, since I do see COMMIT statements in the log output.
For instance, rearranging the below to:
user = User.query.filter_by(id=1).first()
user.x = user.x + 1
elixir.session.commit()
results in a BEGIN, SELECT, UPDATE, COM
