Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email firstname.lastname@example.org
From: Krishna Chandra Prajapati (prajapatikcgmail.com)
Date: Mon Oct 01 2007 - 02:54:21 CDT
The answers are as below
I have not upgraded the server. Done tuning on my.cnf on innodb parameters.
No i have not change the storage engine from MYISAM to INNODB
On 9/28/07, Baron Schwartz <baronxaprb.com> wrote:
> Krishna Chandra Prajapati wrote:
> > Hi All,
> > I am using mysql-client 5.0.15 on fedora system. Server is a Debian box
> > mysql 5.0.32
> > After getting connected to the server(192.168.1.7) using the command
> > mysql -h 192.168.1.7 -D dip -u dip -p
> > When a record deleted from a table on server (192.168.1.7) Then that
> > are not reflected on the client session. If i log out and then reconnect
> > server then the changes are reflected. Earlier it was working fine.
> This is not a bug in the client. It sounds like you are seeing the
> effects of REPEATABLE READ transaction isolation level. Did you upgrade
> the server or reconfigure it? Did you change your storage engine from
> MyISAM to InnoDB?
> The next time this happens, try running COMMIT and then run the SELECT
> again. Do you see the changed data? If so, it's the transaction
> isolation level.