lp:~richardboulton/storm/sqlite-readonly
- Get this branch:
- bzr branch lp:~richardboulton/storm/sqlite-readonly
Branch merges
Related bugs
Related blueprints
Branch information
Recent revisions
- 180. By Richard Boulton
-
Don't complain if remove_
flush_order( ) is called on a readonly Store - it
doesn't cause any change, and is called perfectly legitimately by
Relation.unlink(). - 179. By Richard Boulton
-
Note in a property of an sqlite readonly connection that the connection is
readonly, and test for this property existing and being True when opening a
Store. If it is, override methods which would lead to a change in the database
with variants which raise a ProgrammingError, complaining that the connection
is read-only. - 177. By Richard Boulton
-
Add test that we get the right class returned if we use the readonly option in
a sqlite URI. - 174. By Richard Boulton
-
Basic implementation of readonly sqlite databases, using "readonly=1"
parameters in the URI. Untested as yet. - 172. By Jamu Kakar
-
Merged store-name [r=michelp,radix] [f=131221]
The new ZStorm.get_name method returns the name of the specified
Store, or None if a name isn't available. In addition, ZStorm uses
weak references internally to avoid keeping objects in memory
unnecessarily.