[Sqlalchemy-tickets] [sqlalchemy] #2861: Hazard during versioning records
Brought to you by:
zzzeek
|
From: sqlalchemy <mi...@zz...> - 2013-11-08 21:17:28
|
#2861: Hazard during versioning records
------------------------+--------------------------------------------
Reporter: bikbit | Owner: zzzeek
Type: defect | Status: new
Priority: medium | Milestone: 0.8.xx
Component: utils | Severity: very major - up to 2 days
Keywords: versioning | Progress State: awaiting triage
------------------------+--------------------------------------------
Problem description:
Two requests from client application works on this same record in short
period of time and sometimes appears integrity error from database on
compound key of historical record: id,version.
My guess/investigations:
When two requests perform operation on this same database record and for
example first finished operation, then second have not actual information
about newest version of historical record and try to save new one with
this same version as first.
Versioning used from example of SqlAlchemy and trigered in event
before_flush.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2861>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|