Ticket #1154 (new defect)

Opened 2 years ago

Last modified 4 months ago

SQLObject returning random old data

Reported by: italomaia Assigned to:
Priority: high Milestone: __unclassified__
Component: SQLObject Version: 1.0b1
Severity: critical Keywords: sqlobject, old data, cache
Cc:

Description

After a update, sqlobject sometimes returns old data. Some times it returns the new data as well. Here's a workaround as suggested here: link 

SQLObjectBaseClass._connection.cache.allSubCaches():
cache.clear()

This guy had the same problem: link

Attachments

1154.tar.gz (1.1 kB) - added by jayhem on 11/09/06 05:25:23.
test case

Change History

10/22/06 09:16:39 changed by italomaia

  • owner changed from anonymous to italomaia.
  • status changed from new to assigned.

10/22/06 09:17:13 changed by italomaia

  • owner deleted.
  • status changed from assigned to new.

10/22/06 23:17:08 changed by jorge.vargas

we need to provide a way to reproduce this

a) as a tg bug b) as a sqlobject only test.

11/02/06 14:49:35 changed by jorge.vargas

  • milestone changed from 1.0b2 to 1.0b3.

I'm moving this since we need further prove

11/09/06 05:25:23 changed by jayhem

  • attachment 1154.tar.gz added.

test case

11/09/06 05:26:15 changed by jayhem

Please see the thread "old field value reappears" on the turbogears group: "http://groups.google.fr/group/turbogears/browse_thread/thread/318d32bda9ebf47f/9cdf0540a1b91040#9cdf0540a1b91040"

I created a simple testcase, which reproduces the problem for SO+Sqlite. If I switch to SO+MySQL the problem disappears.

Please find attached the necessary files to run the testcase (just drop them in a default TG project called "bug")

Hope this can be fixed soon, as it renders TG completely unusable with the default settings in place. Probably the severity should be "blocker" and priority "highest".

11/18/06 07:19:21 changed by italomaia

  • priority changed from normal to high.

01/11/07 14:52:13 changed by alberto

  • milestone changed from 1.0b3 to 1.1.

03/28/07 12:42:03 changed by alberto

  • milestone changed from 1.1 to __unclassified__.

Batch moved into unclassified from 1.1 to properly track progress on the later

02/01/08 18:13:30 changed by khorn

This ticket has been at "high" priority for over a year...any proof/progres/updates?