2012-02-24 01:34:15 +01:00
|
|
|
:class:`Database` -- The underlying notmuch database
|
|
|
|
|
====================================================
|
|
|
|
|
|
|
|
|
|
.. currentmodule:: notmuch
|
|
|
|
|
|
|
|
|
|
.. autoclass:: Database([path=None[, create=False[, mode=MODE.READ_ONLY]]])
|
|
|
|
|
|
|
|
|
|
.. automethod:: create
|
|
|
|
|
|
|
|
|
|
.. automethod:: open(path, status=MODE.READ_ONLY)
|
|
|
|
|
|
2012-04-30 19:48:45 +02:00
|
|
|
.. automethod:: close
|
|
|
|
|
|
2012-02-24 01:34:15 +01:00
|
|
|
.. automethod:: get_path
|
|
|
|
|
|
|
|
|
|
.. automethod:: get_version
|
|
|
|
|
|
|
|
|
|
.. automethod:: needs_upgrade
|
|
|
|
|
|
|
|
|
|
.. automethod:: upgrade
|
|
|
|
|
|
|
|
|
|
.. automethod:: begin_atomic
|
|
|
|
|
|
|
|
|
|
.. automethod:: end_atomic
|
|
|
|
|
|
|
|
|
|
.. automethod:: get_directory
|
|
|
|
|
|
database: add n_d_index_file (deprecates n_d_add_message)
We need a way to pass parameters to the indexing functionality on the
first index, not just on reindexing. The obvious place is in
notmuch_database_add_message. But since modifying the argument list
would break both API and ABI, we needed a new name.
I considered notmuch_database_add_message_with_params(), but the
functionality we're talking about doesn't always add a message. It
tries to index a specific file, possibly adding a message, but
possibly doing other things, like adding terms to an existing message,
or failing to deal with message objects entirely (e.g. because the
file didn't contain a message).
So i chose the function name notmuch_database_index_file.
I confess i'm a little concerned about confusing future notmuch
developers with the new name, since we already have a private
_notmuch_message_index_file function, and the two do rather different
things. But i think the added clarity for people linking against the
future libnotmuch and the capacity for using index parameters makes
this a worthwhile tradeoff. (that said, if anyone has another name
that they strongly prefer, i'd be happy to go with it)
This changeset also adjusts the tests so that we test whether the new,
preferred function returns bad values (since the deprecated function
just calls the new one).
We can keep the deprecated n_d_add_message function around as long as
we like, but at the next place where we're forced to break API or ABI
we can probably choose to drop the name relatively safely.
NOTE: there is probably more cleanup to do in the ruby and go bindings
to complete the deprecation directly. I don't know those languages
well enough to attempt a fix; i don't know how to test them; and i
don't know the culture around those languages about API additions or
deprecations.
2017-08-18 01:14:25 +02:00
|
|
|
.. automethod:: index_file
|
2012-02-24 01:34:15 +01:00
|
|
|
|
|
|
|
|
.. automethod:: remove_message
|
|
|
|
|
|
|
|
|
|
.. automethod:: find_message
|
|
|
|
|
|
|
|
|
|
.. automethod:: find_message_by_filename
|
|
|
|
|
|
|
|
|
|
.. automethod:: get_all_tags
|
|
|
|
|
|
|
|
|
|
.. automethod:: create_query
|
|
|
|
|
|
2017-12-07 12:40:46 +01:00
|
|
|
.. automethod:: get_config
|
|
|
|
|
|
|
|
|
|
.. automethod:: get_config_list
|
|
|
|
|
|
|
|
|
|
.. automethod:: set_config
|
|
|
|
|
|
2012-02-24 01:34:15 +01:00
|
|
|
.. attribute:: Database.MODE
|
|
|
|
|
|
|
|
|
|
Defines constants that are used as the mode in which to open a database.
|
|
|
|
|
|
|
|
|
|
MODE.READ_ONLY
|
|
|
|
|
Open the database in read-only mode
|
|
|
|
|
|
|
|
|
|
MODE.READ_WRITE
|
|
|
|
|
Open the database in read-write mode
|
