Paul Boddie wrote:
> On 4 Feb, 20:30, John Nagle <[EMAIL PROTECTED]> wrote:
>>This has me completely mystified. Some SELECT operations performed
>> through
>> MySQLdb produce different results than with the MySQL graphical client.
>> This failed on a Linux server running Python 2.5, and I can
On 5 feb, 01:42, Steve Holden <[EMAIL PROTECTED]> wrote:
> John Nagle wrote:
> > Carsten Haese wrote:
> >> On Mon, 2008-02-04 at 11:30 -0800, John Nagle wrote:
> >>> Restarting the MySQL instance changes the database. The entry
> >>> "google.com"
> >>> disappears, and is replaced by "www.google.c
John Nagle wrote:
> Carsten Haese wrote:
>> On Mon, 2008-02-04 at 11:30 -0800, John Nagle wrote:
>>> Restarting the MySQL instance changes the database. The entry "google.com"
>>> disappears, and is replaced by "www.google.com". This must indicate a
>>> hanging
>>> transaction that wasn't commit
Carsten Haese wrote:
> On Mon, 2008-02-04 at 11:30 -0800, John Nagle wrote:
>> Restarting the MySQL instance changes the database. The entry "google.com"
>> disappears, and is replaced by "www.google.com". This must indicate a
>> hanging
>> transaction that wasn't committed.
>>
>> But that trans
On Mon, 2008-02-04 at 11:30 -0800, John Nagle wrote:
> Restarting the MySQL instance changes the database. The entry "google.com"
> disappears, and is replaced by "www.google.com". This must indicate a hanging
> transaction that wasn't committed.
>
> But that transaction didn't come from the Pyt
