mirror of
https://git.notmuchmail.org/git/notmuch
synced 2024-11-22 02:48:08 +01:00
doc: forbid further operations on a closed database
We could add many null pointer checks, but currently I don't see a use case that justifies it.
This commit is contained in:
parent
be55acf4f0
commit
38f0d44a82
1 changed files with 3 additions and 1 deletions
|
@ -332,7 +332,9 @@ notmuch_database_status_string (const notmuch_database_t *notmuch);
|
||||||
* functions on objects derived from this database may either behave
|
* functions on objects derived from this database may either behave
|
||||||
* as if the database had not been closed (e.g., if the required data
|
* as if the database had not been closed (e.g., if the required data
|
||||||
* has been cached) or may fail with a
|
* has been cached) or may fail with a
|
||||||
* NOTMUCH_STATUS_XAPIAN_EXCEPTION.
|
* NOTMUCH_STATUS_XAPIAN_EXCEPTION. The only further operation
|
||||||
|
* permitted on the database itself is to call
|
||||||
|
* notmuch_database_destroy.
|
||||||
*
|
*
|
||||||
* notmuch_database_close can be called multiple times. Later calls
|
* notmuch_database_close can be called multiple times. Later calls
|
||||||
* have no effect.
|
* have no effect.
|
||||||
|
|
Loading…
Reference in a new issue