Heri,
- Original Message -
From: ""H. Steuer"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Sent: Tuesday, December 03, 2002 11:49 AM
Subject: Re: C API problems with InnoDB
> Hello Mark,
>
> thanks for your answer. In fact the mysql shel
Heri,
"H. Steuer" schrieb:
>
> Hi Stefan,
>
> > Does the second shell actually perform those changes? In this case, I
> assume
> > it's got something to do with the isolation level / consistent read in
> > InnoDB tables. "shell1" sees all its changes immediately, "shell2" (the
> > application) h
Hi Stefan,
> Does the second shell actually perform those changes? In this case, I
assume
> it's got something to do with the isolation level / consistent read in
> InnoDB tables. "shell1" sees all its changes immediately, "shell2" (the
> application) has just a snapshot of the data at the time it
Hello Mark,
thanks for your answer. In fact the mysql shell where I update the row is
using AUTOCOMMIT=1.
Even after I issue a COMMIT manually the changes are not seen by the
application.
What I dont understand is that the program doing a SELECT has to issue an
COMMIT to have all data available.
M
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
H. Steuer wrote:
Hello MySQL users,
I have a weired issue using the MySQL C API and InnoDB tables.
An application polls a database every 30 seconds. When the application
starts everything seems to be fine.
During the running of the application i chan
Dear Heri,
> I tracked down the problem and saw that its only happening if I set
> autocommit=0.
> If I run a second mysql shell I can see all changes immediately. Just the
> application itself doesnt.
Does the second shell actually perform those changes? In this case, I assume
it's got something
