id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
11248	Multiple connections; different query results. with mysql innodb engine	Lloyd <lloyd@…>	nobody	"This is always reproducable with innodb, but works as expected w/ postgres or myiasm
With a simple model and caching disabled.
create a instance in the admin interface and save
in a manage.py shell load the instance ( .get() or .all()[0])
change the instance in the admin and save
reload the instance in the shell (.get() or .all()[0])
 the shell instance is the __old__ version that seems to be cached !!
Same problem between 2 shells or if you change in a shell and refresh the admin page.
The save is happening and all looks well if you inspect tables with mysqls client after save, so problem seems to be on retrieval side.

Thanks in advance,
 --Lloyd

django v 1.0.2
MySQLdb v 1.2.2
mysql  Ver 14.14 Distrib 5.1.31, for sun-solaris2.10 (sparc)
Python 2.5.4 (r254:67916, Jan 16 2009, 17:22:03) 
IPython 0.9.1 -- An enhanced Interactive Python.
"		closed	*.djangoproject.com	1.0		invalid	innodb mysql cached		Unreviewed	0	0	0	0	0	0