On Nov 10, 2007, at 12:20 PM, david wrote:
>
> Hi Mike -
>
> That did the trick!
>
> But, the strange thing is, if you note the illustration above, for
> both situations I was selecting on a key, and there was only a single
> row for each. Why would one require the result.close(), and the other
Hi Mike -
That did the trick!
But, the strange thing is, if you note the illustration above, for
both situations I was selecting on a key, and there was only a single
row for each. Why would one require the result.close(), and the other
not?
Yes, I wasn't sure the error is that all important -
On Nov 10, 2007, at 1:44 AM, david wrote:
>
>
> Here's an example - 2 tables author_t, and keyword_t
>
> author_t = Table('author', meta,
> Column('authorkey', Unicode(35), primary_key=True),
> Column('lastname', Unicode),
> Column('firstname', Uni
Well, Michael, what you say sounds reasonable. However, I think
something more strange is going on (unless I am making a very stupid
mistake, which is entirely likely)
I am using the current pylons framework. I have tried to follow their
recommendations to the letter. All of my queries are in a s
On Nov 8, 2007, at 10:11 PM, david wrote:
>
>
> Any ideas on how to fix, or what the nature of the issue is, or how to
> better isolate/debug would be much appreciated.
>
its most lkely concurrent access on a single mysql connection. ensure
that you arent sharing a single instance of Session
