• Kirill Smelkov's avatar
    FileStorage: Report problem on read-only open of non-existent file · 56c96a11
    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.
    
    (cherry picked from commit 30bbabf1)
    56c96a11
Name
Last commit
Last update
doc Loading commit data...
src/ZODB Loading commit data...
.coveragerc Loading commit data...
.gitignore Loading commit data...
.travis.yml Loading commit data...
3.11.txt Loading commit data...
CHANGES.rst Loading commit data...
COPYING Loading commit data...
COPYRIGHT.txt Loading commit data...
DEVELOPERS.rst Loading commit data...
HISTORY.txt Loading commit data...
LICENSE.txt Loading commit data...
MANIFEST.in Loading commit data...
README.rst Loading commit data...
bootstrap.py Loading commit data...
buildout.cfg Loading commit data...
ez_setup.py Loading commit data...
log.ini Loading commit data...
release.py Loading commit data...
setup.py Loading commit data...
tox.ini Loading commit data...