[Rpm-maint] [rpm-software-management/rpm] Revert back to implicit database creation for now (#1654)

[Panu Matilainen]

The implicit database creation even on read-only access is rooted so
deep in so many places that this needs more thought and saner APIs.
While creating databases on read-only access remains a crazy thing to
do, we need to have a proper solution to point people to when changing
the behavior, and right now we don't.

This effectively reverts 86f593d5135b00a9dbf7dc6d5efc8b341002aa08,
d601a7b7ae764b31ad74b2dceff1eafb5297147f and
afbc2b07839c9ffe9f274f3a4bc2395c76d65472, but adopting 4.16.x version
of the sqlite open error message to avoid accessing freed handle, and
leaving the testcase for query on non-existent db in place (just
changing the expected result) as this is a rather fundamental behavior thing.
You can view, comment on, or merge this pull request online at:

  https://github.com/rpm-software-management/rpm/pull/1654

-- Commit Summary --

  * Revert back to implicit database creation for now

-- File Changes --

    M lib/backend/ndb/glue.c (4)
    M lib/backend/sqlite.c (21)
    M lib/depends.c (6)
    M lib/rpmdb.c (5)
    M tests/rpmdb.at (2)

-- Patch Links --

https://github.com/rpm-software-management/rpm/pull/1654.patch
https://github.com/rpm-software-management/rpm/pull/1654.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/1654
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20210426/7f7f869d/attachment.html>