If somebody is opening a database in a read-only mode (eg for query then we
really have no business to *create* such database if not existing.
This implicit discard of read-only flag is such a long standing behavior that
this is likely to break stuff here and there.
You can view, comment on, or merge this pull request online at:
https://github.com/rpm-software-management/rpm/pull/1443
-- Commit Summary --
* Stop on first failure when trying to open a database (RhBug:1898301)
* Disable implicit database creation on read-only handle
-- File Changes --
M lib/backend/db3.c (5)
M lib/backend/ndb/glue.c (2)
M lib/backend/sqlite.c (6)
M lib/rpmdb.c (2)
M tests/local.at (2)
M tests/rpmdb.at (13)
M tests/rpmpython.at (4)
-- Patch Links --
https://github.com/rpm-software-management/rpm/pull/1443.patch
https://github.com/rpm-software-management/rpm/pull/1443.diff
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1443
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
