I removed SQLSoup and the caching/stale results issues are gone now.
Have to wait a little longer to see if there is any bearing on the
MySQL has gone away/invalid transaction thing.
Changing the default beaker timeout to something small, like 15 secs,
doesn't seem to fix things.
Thanks for all
Unfortunately, from a support-seeker point of view, such rhetoric is
often necessary. How many times have you written a mailing list or hit
up an IRC channel and had everyone write you off as incompetent just
by default when they can't figure something out? It's important to
establish that I _do_
On Oct 17, 6:49 pm, Jeff Cook cookieca...@gmail.com wrote:
Unfortunately, from a support-seeker point of view, such rhetoric is
often necessary. How many times have you written a mailing list or hit
sqlalchemy.pool_recycle = 10
I had odd issues -- even though mysql was set to
|
Thanks for the help. I wasn't assigning the session to SQLSoup's
session, but I am now, and I'm still getting stale data and I don't
know yet if I'll still be getting the invalid transaction/MySQL has
gone away thing. I think I'll try just taking SQLSoup out of the thing
all together and try
On Oct 15, 11:50 pm, Jeff Cook cookieca...@gmail.com wrote:
So, SQLAlchemy is doing something here. There probably is some
incorrect code in my program, which is why I am writing this list, to
figure out what that is. I'm an experienced developer and I don't
appreciate your disrespect. I can
Jeff Cook wrote:
Dear All People:
I'm using SQLSoup and getting errors like InvalidRequestError: Can't
reconnect until invalid transaction is rolled back and MySQL Server
has gone away. I have set autoflush=True and this has helped mitigate
some errors, but not these, they happen with
It's not faster. I use pyscopg2 directly on some other projects and
it's definitely a lot faster to just be able to write the query I want
than to try to think of how to convert it to SQLAlchemy's contexts and
functions. Maybe it's just learning curve thing, but as shown, I can't
get that join to
Jeff Cook wrote:
I don't fully understand what you're talking about. I have this error
and I need to make it stop. I just want SQLAlchemy to connect, run the
query I instructed, and give me the results back and do this reliably
without necessitating consistent server restarts. Thus far, it's
I see. So Pylons should handle this by default, but it's not doing so?
That's highly disappointing. Clearly, something is quite incorrect
here. Is my usage of SQLSoup causing rollback not to run?
On Thu, Oct 15, 2009 at 1:16 PM, Michael Bayer mike...@zzzcomputing.com wrote:
Jeff Cook wrote:
I
And when things _do_ work, there are serious caching problems.
Sometimes it gives me the transaction rollback error, sometimes it
gives me an old version of the page, and sometimes it gives me a
current version of the page. I assume this has something to do with
what connection is getting used.
On Oct 15, 2009, at 3:32 PM, Jeff Cook wrote:
And when things _do_ work, there are serious caching problems.
Sometimes it gives me the transaction rollback error, sometimes it
gives me an old version of the page, and sometimes it gives me a
current version of the page. I assume this has
OK, man, well, I have one function that has the calls to perform the
listing. I refresh and sometimes get old data and sometimes don't.
There is no clustering and no other databases, there is no possibility
that the server is retrieving old data. I haven't changed the base
Pylons classes at all,
12 matches
Mail list logo
