| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
Port references and links to the gi-docgen format, and while at
it flesh out some more documentation and adjust formatting to
look better with the gi-docgen templates.
|
| |
|
|
|
| |
The documentation of g_dbus_error_register_error_domain() says we
should not use one.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Right now the handling of those is somewhat inconsistent, we
loudly warn, but simply return FALSE from our stmt_step() function
without setting an error. Fortunately, the most common reason for
those errors has been the soft corruption resulting from FTS
index corruption, so continuing despite the error was alright.
Propagate these error situations properly through a new
TRACKER_SPARQL_ERROR_CORRUPT error code, so that callers can
fail, rollback, or otherwise react upon.
|
| |
|
|
|
|
|
| |
We want to stop making this a separate static library, but internal to
libtracker-sparql. As a first step, move it into libtracker-sparql and
use a cooler yet more honest name, this really is the core of our
SPARQL and RDF storage implementation.
|
| |
|
|
|
| |
Add a new error code for this specific error situation when parsing the
database ontology. Based on code by Abanoub Ghadban <abanoub.gdb@gmail.com>.
|
| |
|
|
|
| |
Add a new error code for this specific error situation when parsing the
database ontology. Based on code by Abanoub Ghadban <abanoub.gdb@gmail.com>.
|
| |
|
|
| |
Necessary to put things together nicely in hotdoc.
|
| |
|
|
|
|
|
|
| |
The error->domain checks are mutually exclusive, so do this in
if/else branches instead of separate ifs. This does not change
functionality, just made to help readability and coverity.
CID: #1501115
|
| |
|
|
|
| |
And add the missing plumbing for TRACKER_SPARQL_ERROR_CONSTRAINT to
be a thing.
|
| |
|
|
| |
This shouldn't be public, we already register the DBus error strings.
|
|
|
We should not return TrackerDBInterfaceError, from the internal
libtracker-data library, from public functions in libtracker-sparql.
This problem is noticable as we register D-Bus error codes only for the
public TrackerSparqlError type.
Before, apps would show error messages like this:
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._tracker_2ddb_2dinterface_2derror_2dquark.Code0: example error message
After this patch, the error is:
GDBus.Error:org.freedesktop.Tracker.Error.QueryFailed: example error message
|
