Question

Django(价值1.1.4的改动)是任意的,没有发现属于我数据库表之一的项目。所涉物体经理是违约者。下面有两个例子,第一个例子说明问题的范围,第二个例子提供了具体事例。

Django:

In [5]: LocalStore.objects.all().count()
Out[5]: 1466

MySQL:

mysql> select count(*) from stores_localstore;
+----------+
| count(*) |
+----------+
|     1553 | 
+----------+
1 row in set (0.00 sec)

其本身就足够了。如今,就是一个单一物体的例子,该物体在非行,但 is:

Django:

In [37]: LocalStore.objects.filter(id=474361)
Out[37]: []
In [39]: print LocalStore.objects.filter(id=474361).query
SELECT `stores_localstore`.`id`, `stores_localstore`.`cust_id`,
`stores_localstore`.`name`, `stores_localstore`.`lat`, `stores_localstore`.`lng`,
`stores_localstore`.`addr1`, `stores_localstore`.`addr2`, `stores_localstore`.`city`, 
`stores_localstore`.`email`, `stores_localstore`.`fax`, `stores_localstore`.`phone`, 
`stores_localstore`.`state`, `stores_localstore`.`url`, `stores_localstore`.`zip` FROM
`stores_localstore` WHERE `stores_localstore`.`id` = 474361

出于隐私原因,我不想向大家展示我SQL问答的准确结果,但只需说,这确实是回到数据库。

这给我造成了非常奇怪的行为,有可能给Django ORM的头盔带来深.。但我也有可能忽视一些显而易见的事情。这怎么办?

Answer 1

Django正在寻找一个与你连接的不同数据库,或者说你已告诉Django去做一些事情。 Django没有数据。

1. 证实django与正确数据库有关:

from django import db
db.settings.DATABASES.get( default )

Answer 2

Possibly the isolation level of your MySQL is REPEATEABLE READ(which is default for innodb), and the DB connection in Django shell is in a transaction earlier than the new inserting of rows(caused by manually transaction management or using of some connection-pool, etc) and still holds an expired snapshot of old rows.
Then you experienced phantom reading.

友情链接