- 07 Apr, 2017 1 commit
-
-
Jim Fulton authored
-
- 02 Apr, 2017 2 commits
-
-
Jim Fulton authored
FileStorage: Report problem on read-only open of non-existent file
-
Kirill Smelkov authored
... instead of silently creating empty database on such opens. Use-case for this are utilities like e.g. zodbdump and zodbcmp which expect such storage opens to fail so that the tool can know there is no such storage and report it to user. In contrast current state is: read-only opens get created-on-the-fly empty storage with no content, but which can be iterated over without getting any error. This way e.g. `zodbdump non-existent.fs` produces empty output _and_ exit code 0 which is not what caller expects.
-
- 27 Mar, 2017 1 commit
-
-
Adam Groszer authored
-
- 21 Mar, 2017 2 commits
-
-
Jim Fulton authored
Add info on Newt DB
-
Maik Röder authored
-
- 19 Feb, 2017 2 commits
-
-
Godefroid Chapelle authored
-
Godefroid Chapelle authored
For the record, I udes `zest.releaser` `longtest` script to debug...
-
- 09 Feb, 2017 6 commits
-
-
Jim Fulton authored
-
Jim Fulton authored
-
Jim Fulton authored
-
Jim Fulton authored
TransactionUndoStorage tests close the conn and db
-
Jim Fulton authored
Notify storages that transactions have completed.
-
Jim Fulton authored
Where it makes more sense. Hysterically, it didn't matter because one was an alias for the other.
-
- 08 Feb, 2017 3 commits
-
-
Jim Fulton authored
-
Jim Fulton authored
For safety, closing the database aborts transaction managers associated with open connections. In explicit mode, this can lead to NoTransaction errors. It's likely a bug for DB objects to abort transactons on close. This needs more thought.
-
Jim Fulton authored
resources after transaction complete. See: https://github.com/zodb/relstorage/issues/147 - Take advantage of the new transaction-manager explicit mode to avoid starting transactions unnecessarily when transactions end.
-
- 01 Feb, 2017 2 commits
-
-
Jim Fulton authored
Don't manipulate Connection state after it has been returned to the pool. Good catch. Thanks.
-
Jason Madden authored
Doing so leads to race conditions. In particular, there can be an AttributeError. See https://github.com/zodb/zodbshootout/issues/26 for details.
-
- 28 Jan, 2017 6 commits
-
-
Jim Fulton authored
Don't require persistent at setup time. We don't build native code th…
-
Jason Madden authored
Don't require persistent at setup time. We don't build native code that needs those headers anymore. Fixes #119.
-
Jim Fulton authored
Connection.new_oid delegates to its storage, not the DB.
-
Jason Madden authored
-
Jason Madden authored
This fixes leaking connections (relying on the GC to close them). Tested with RelStorage. Fixes #138
-
Jason Madden authored
Fixes #139
-
- 20 Dec, 2016 1 commit
-
-
Jim Fulton authored
-
- 18 Nov, 2016 6 commits
-
-
Jim Fulton authored
-
Jim Fulton authored
Fixed: ZODB.Connection.TransactionMetaData didn't custom data
-
Jim Fulton authored
-
Jim Fulton authored
-
Jim Fulton authored
storage that some storages rely on.
-
Jim Fulton authored
sigh
-
- 17 Nov, 2016 8 commits
-
-
Jim Fulton authored
-
Jim Fulton authored
transaction user and description: text above, bytes below
-
Jim Fulton authored
-
Jim Fulton authored
-
Jim Fulton authored
-
Jim Fulton authored
-
Jim Fulton authored
Also added _s to _transaction_meta_data_text_variables and _text_transaction_info to mark them as private.
-
Jim Fulton authored
-