lp:~edoardo-serra/storm/select-for-update-support

Branch merges

Propose for merging

No branches dependent on this one.

Ready for review for merging into lp:storm

Storm Developers: Pending requested 2010-09-10

Storm Developers: Pending requested 2010-09-10

Diff: 510 lines (+188/-18)

6 files modified

storm/databases/sqlite.py (+4/-0)
storm/expr.py (+7/-3)
storm/store.py (+51/-14)
storm/zope/interfaces.py (+3/-0)
tests/expr.py (+13/-1)
tests/store/base.py (+110/-0)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Bug #499363: Provide some way to do "SELECT ... FOR UPDATE"

Undecided

New

Link a bug report

Related blueprints

380. By Edoardo Serra <eserra@barbera> on 2010-09-09

SELECT ... FOR UPDATE implemented in Store.get

379. By Edoardo Serra <eserra@barbera> on 2010-09-08

Unit tests

378. By Edoardo Serra <eserra@barbera> on 2010-09-08

SELECT ... FOR UPDATE is not compatible with GROUP BY

377. By Edoardo Serra <eserra@barbera> on 2010-09-08

SQLite does not support SELECT ... FOR UPDATE

376. By Edoardo Serra <eserra@barbera> on 2010-09-08

Starting implementation of SELECT ... FOR UPATE

375. By Free Ekanayaka on 2010-09-07

Merge storm-testresource [f=618704] [r=jkakar,therve]

This branch adds a storm.zope.testing.ZStormResourceManager class to
manage a set of stores registered with ZStorm.

374. By Thomas Herve on 2010-09-01

Merge resultset-select-copy [r=niemeyer,jkakar] [f=620508]

Give a copy the _select attribute when ResultSet.copy is called, to prevent problems
when _get_select modifies it later on. It fixes a problem with sliced results
and count calls, mainly.

373. By James Henstridge on 2010-08-20

Compatibility fixes for psycopg2 >= 2.2.
[r=therve,jdobrien] [f=585704]

372. By Thomas Herve on 2010-08-19

Merge loaded-bug-619017 [r=jkakar,lifeless,niemeyer] [f=619017]

Make sure that all variables are defined when an object comes out of the cache
and __storm_loaded__ is called.

371. By Free Ekanayaka on 2010-08-18

Merge schema-support [f=250412] [r=niemeyer,jkakar]

The schema management code used by the Landscape project has been
included under storm.schema, allowing to define Schema objects for
creating, dropping, clearing and upgrading database schemas across
multiple databases. The patch system is file-based, i.e. each database
patch is defined in a separate file inside a Python module directory.

See storm.schema.patch.PatchApplier and storm.schema.schema.Schema for
more details.