Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Z
ZODB
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Kirill Smelkov
ZODB
Commits
6e9247ba
Commit
6e9247ba
authored
Feb 15, 2006
by
Chris McDonough
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add forgotten todos.
parent
86046df2
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
21 additions
and
0 deletions
+21
-0
src/ZODB/Blobs/TODO.txt
src/ZODB/Blobs/TODO.txt
+21
-0
No files found.
src/ZODB/Blobs/TODO.txt
View file @
6e9247ba
...
...
@@ -33,6 +33,27 @@ Production
- Importing backward compatible ZEXP files (no \0BLOBSTART) used
- Test Connection.TmpStore.storeBlob better. Why doesn't it do any
locking like normal storages do? It also needs to clean up its
tempfiles.
- abort is never called on a BlobStorage when a transaction is
aborted... it couldn't have been because there was basically a bit
of nonsensical code in the method that would have raised an
exception. I don't think we solved this. I think we did figure out
why it wasn't called -- it seems that methods of a
zope.proxy-wrapped object aren't rebound to the wrapper but instead
to the wrapped object. I then tried every which way to have some
cleanup code invoked on abort (overriding "tpc_abort" instead of
"_abort", overriding "abort" instead of "_abort") but without
success. Late in the day I think we figured that the abort cleanup
code might need to go in the "BlobDataManager" (each blob has its
own data manager) instead of the BlobStorage because it's unclear
when BlobStorage's tpc_abort/_abort/abort methods will be called.
- Savepoints: currently non-optimistic savepoints in transactions
which involve blobs don't work. Is this OK?
Far future
----------
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment