On Nov 12, 9:45 pm, Christoph Zwerschke <[EMAIL PROTECTED]> wrote:
> imix wrote:
> > I updated my system to turbogears 1.0.4b2 with SQLAlchemy 0.4. I now
> > see sometimes an InvalidRequestError when running a DB query.
>
> > This happens on my own project (with mysql) and a quickstarted project
> > (with sqlite). Below is a small piece of code on a quickstarted
> > project that generates the error for me (i've seen the problem also
> > outside of a scheduler job and with other tables than the Visit table
> > but this way it seems easyest to reproduce).
>
> I have tried this under Windows with the current head of 1.0, and I
> don't see this problem. I'm logging in from two different browsers and I
> see the print statements for both sessions from your some_test() method,
> and I see them vanish after visit.timeout seconds. No error appears.
>
> Are you doing something different from logging in with a browser?

I'm actually doing nothing, just running the scheduler task leads to
the exception. (no need for an entry in the Visit table)

On my own project I sometimes saw the problem when navigating pages.
If it happened,
a reload made it go away. Strangely the scheduled case does the
inverse. First time the query runs
ok, second time it no longer works (so far every time).

> Can you try again with the current head from SVN?

I tried and so far I was not able to reproduce the problem with the
current head. So either the
problem is gone or it has become much less frequent (as the case from
the scheduled job never
happened this does not seem very probable though). With 1.0.4b2 it can
still be easily reproduced.

regards

Stefan


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to