Re: Object caching in a mod_perl application

[prev] [thread] [next] [Date index for 2005/03/17]

Michael Peters wrote:

> Jim Mozley wrote: 
>> One other email I've come across also asked if the poster was using 
>> InnoDB tables. I am and wondered if there was a particular issue with 
>> these?
> 
> 
> It could be. By default MySQL with InnoDB has a slighly non-intuitive 
> transaction isolation level, 'REPEATABLE-READ'. It means that other 
> processes cannot seen data, even committed data, until they themselves 
> perform a commit.
> 
> I normally use 'READ-COMMITED' which means that as soon as one process 
> commits the change, any other can see it.

I will look into setting this. InnoDB seemed a better way to go for the 
introduction of foreign key constraints and transactions, although I'm 
not using any of this at present.

> I saw your update() call but 
> did not see where you committed, so this may or may not help.

I thought the default was auto-commit (seems to be in the docs) and I 
haven't changed this. I'm not doing an explicit commit anywhere, but I 
know that changes do update the DB.

Regards,

Jim Mozley