On 7 Feb, 08:52, Frank Aune <[EMAIL PROTECTED]> wrote:
> On Wednesday 06 February 2008 16:16:45 Paul Boddie wrote:
>
> > Really, the rule is this: always (where the circumstances described
> > above apply) make sure that you terminate a transaction before
> > attempting to read committed, updated d
On Wednesday 06 February 2008 16:16:45 Paul Boddie wrote:
> Really, the rule is this: always (where the circumstances described
> above apply) make sure that you terminate a transaction before
> attempting to read committed, updated data.
How exactly do you terminate a transaction then?Do you term
On 6 Feb, 16:04, Frank Aune <[EMAIL PROTECTED]> wrote:
>
> Whenever I did a SELECT() on the first connection, the cursor would
> stop "seeing" new entries commited in the log table by the other connection.
> I always assumed you needed COMMIT() after adding new content to the
> database, not after
On Tuesday 05 February 2008 18:58:49 John Nagle wrote:
> So you really do have to COMMIT after a SELECT, if you are reusing
> the database connection. CGI programs usually don't have this issue,
> because their connections don't live long, but long-running FCGI (and maybe
> Twisted) programs d
Steve Holden 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.com". This must indicate
a hanging
>
