summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* libtracker-data: Lighten up TrackerSparql structwip/carlosg/sparql-stateCarlos Garnacho2020-09-161-655/+681
| | | | | | | | | | There is an internal struct carrying the parser state, this struct began small, but kept growing. This state is actually unneeded after parsing, so we can keep TrackerSparql smaller, and only allocate the state transiently during parsing. Since TrackerSparql is the basis for TrackerSparqlStatement, this should help memory usage a tiny bit if many prepared statements are cached.
* Update Slovak translationDušan Kazik2020-09-161-98/+89
|
* docs: Fix typo in examplesCarlos Garnacho2020-09-152-2/+2
| | | | | The error checks are the wrong way around. Introduced in commits f8282a29e5 and 87e189d5a0. Spotted again by coverity.
* Merge branch 'wip/carlosg/coverity-fixes' into 'master'Carlos Garnacho2020-09-157-12/+26
|\ | | | | | | | | Fixes for Coverity warnings See merge request GNOME/tracker!312
| * libtracker-data: Remove no-op functionwip/carlosg/coverity-fixesCarlos Garnacho2020-09-141-2/+0
| | | | | | | | | | | | | | This function is a getter, and its return value ignored. Spotted by Coverity. CID: #1491437
| * libtracker-fts: Check sqlite3_exec() return valueCarlos Garnacho2020-09-141-1/+4
| | | | | | | | | | | | Spotted by Coverity. CID: #1492511
| * docs: Avoid dead expressions in code examplesCarlos Garnacho2020-09-141-3/+3
| | | | | | | | | | | | Spotted by Coverity. CID: #1491750
| * docs: Avoid dead expressions in code examplesCarlos Garnacho2020-09-141-3/+3
| | | | | | | | | | | | Spotted by Coverity. CID: #1491749
| * docs: Avoid dead expression in code exampleCarlos Garnacho2020-09-141-1/+1
| | | | | | | | | | | | Spotted by Coverity CID: #1491748
| * libtracker-data: Ensure there is an error on all failure pathsCarlos Garnacho2020-09-141-1/+14
| | | | | | | | | | | | | | The services virtual table filter() function implementation was missing a GError in some failure paths. Spotted by Coverity. CID: #1491444
| * tests: Silence checkCarlos Garnacho2020-09-141-1/+1
| | | | | | | | | | | | | | Coverity seems to deem it possible to leak a variable after ensuring it is NULL. Assert NULLability harder. CID: #1496664
* | Update Dutch translationNathan Follens2020-09-141-1459/+1205
|/
* Release 3.0.03.0.0Carlos Garnacho2020-09-132-1/+6
|
* Update Latvian translationRūdolfs Mazurs2020-09-131-1392/+1166
|
* Update Kazakh translationBaurzhan Muftakhidinov2020-09-121-185/+149
|
* Updated Danish translationAsk Hjorth Larsen2020-09-121-194/+202
|
* Update Italian translationMilo Casagrande2020-09-101-2527/+239
|
* Update German translationStephan Woidowski2020-09-081-193/+195
|
* Updated Danish translationAsk Hjorth Larsen2020-09-081-2474/+241
|
* Update Korean translationSeong-ho Cho2020-09-081-2922/+253
|
* Release 2.99.52.99.5Carlos Garnacho2020-09-072-1/+18
|
* Merge branch 'wip/carlosg/fix-manpages-install' into 'master'Carlos Garnacho2020-09-077-76/+80
|\ | | | | | | | | Fix manpages install See merge request GNOME/tracker!311
| * manpages: Fix installation of manpage filesCarlos Garnacho2020-09-071-11/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The xsltproc step has two small gotchas: the output does not happen on stdout, so we are capturing empty stdout, and installing an empty file instead of our nice manpages. But also, the target filename gets determined by the XSL based on the input, so a manpage filename is as defined in its NAME section. This means we cannot do filename changes to add the version this late in the stage. Furthermore, the tracker-xdg-portal-3 manpage follows a different naming scheme (i.e. not "tracker3-*"). Handle this all at once, specify per manpage target files that do match the xsltproc output, and ensure the file gets generated at the current build dir.
| * manpages: Reference daemons with their executable nameCarlos Garnacho2020-09-071-4/+4
| | | | | | | | | | | | | | | | | | | | Those are now versioned, so reference them as such in their respective manpages. Note: The name change also changes the target manpage file written by our xsltproc step, since it is defined by the file+xsl. This will silently go ignored, as installation of manpages is broken (we install empty files). This will get fixed in later commits.
| * manpages: Update references to the tracker3 CLI toolCarlos Garnacho2020-09-075-61/+61
|/ | | | | | | | | | | We did reference it in manpages as simply "tracker", which is definitely not going to be the case. Make CLI examples, titles and section names correctly reference the real "tracker3" name. Note: The name change also changes the target manpage file written by our xsltproc step, since it is defined by the file+xsl. This will silently go ignored, as installation of manpages is broken (we install empty files). This will get fixed in later commits.
* Update Swedish translationAnders Jonsson2020-09-061-302/+397
|
* Update Hungarian translationBalázs Úr2020-09-041-287/+409
|
* Updated Slovenian translationMatej Urbančič2020-09-041-8/+10
|
* Merge branch 'wip/carlosg/fts5-syntax-under-the-rug' into 'master'Sam Thursfield2020-09-0413-5/+31
|\ | | | | | | | | | | | | libtracker-data: Do not expose FTS5 syntax through fts:match Closes gtk#3114 See merge request GNOME/tracker!310
| * tests: Add FTS tests for some extraneous inputCarlos Garnacho2020-09-038-0/+12
| | | | | | | | Test dots and quotes in input so far.
| * libtracker-data: Do not expose FTS5 syntax through fts:matchCarlos Garnacho2020-09-035-5/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We used to simply forward all FTS match string interpretation to SQLite's FTS implementation, and used to allow and announce its features, e.g. use of AND/OR keywords for more complex matches. When FTS5 came through, the FTS query syntax got a major revamp, also in the complexity of the allowed syntax, including non natural language (e.g. symbols like ^ or *). This makes all the gory details of this parser available to users, but also its pitfalls, e.g. execution-time errors are raised when the search string contains special symbols non-interpretable by the FTS5 parser. Since fts:match is often plugged directly to search entries in UIs around, it seems a bad approach to maybe fail the query or not depending on the last character entered. Arguably applications might cater for this additional level of syntax, but it's sadly not trivial and kind of a moving target (fts5 still does add features from time to time), seems bad to leave this up to applications. So, hide all FTS5 syntax from the upper layers. The fts:match string forcibly becomes '"%s"*' so it is ensured that all the input string is interpreted as "search terms". It is also ensured that the given search string cannot break out of that. The '*' character makes the last term in the search string be interpreted as a prefix search. We lose some neat things there, like AND/OR mentioned above, or the possibility to match a single property instead of a whole row. AND is already the default, OR can be obtained through additional fts:match, and the last one is a rather obscure feature. Might be neat to bring back in another form someday. (e.g. make fts:match a FILTER function). Also, update tests to these new expectatives. Fixes: https://gitlab.gnome.org/GNOME/gtk/-/issues/3114
* | Update Catalan translationJordi Mas2020-09-041-177/+173
|/
* Update Slovak translationDušan Kazik2020-09-031-1467/+1230
|
* Merge branch 'wip/carlosg/2to3-export' into 'master'Sam Thursfield2020-09-024-5/+202
|\ | | | | | | | | Add --2to3 exporting capabilities to `tracker3 export` See merge request GNOME/tracker!308
| * tracker: Add --2to3 switch to "tracker3 export"Carlos Garnacho2020-09-022-4/+200
| | | | | | | | | | | | | | | | | | | | This special mode opens the old Tracker2 database, and tries to extract data, pretty much in the same fashion than "tracker export" command introduced recently in 2.3.x. So far, this submode only supports exporting of starred files. The --keyfile argument is also supported, to ease manipulation of this data on the consumer side.
| * libtracker-data: Add flag to drop version checksCarlos Garnacho2020-09-022-1/+2
| | | | | | | | Only for internal use, and with plenty of care.
* | Updated Slovenian translationMatej Urbančič2020-09-011-38/+26
| |
* | Added Czech stop-wordsMarek Černocký2020-09-012-0/+243
|/
* libtracker*: Do not export symbols from static librariesCarlos Garnacho2020-09-012-1/+3
| | | | | We let libtracker-sparql tie everything together, specify that these libraries don't export symbols.
* build: Remove outdated commentsSam Thursfield2020-09-012-4/+0
| | | | | | Meson issue https://github.com/mesonbuild/meson/issues/671 was fixed years ago and we can use tracker_common_dep anywhere we like without fear of combinatorial explosion.
* Merge branch 'wip/carlosg/libtracker-data-static' into 'master'Sam Thursfield2020-09-012-4/+2
|\ | | | | | | | | libtracker-data: Make a static library See merge request GNOME/tracker!307
| * libtracker-data: Make a static libraryCarlos Garnacho2020-09-011-3/+1
| | | | | | | | | | | | | | | | | | | | There's no multiple executables pulling this library directly. We have some direct uses of this library, but they are all tests and non-install executables in the repo. Making it a static library won't increase install size, as only libtracker-sparql pulls from it in the system, that's what everyone should use instead.
| * libtracker-sparql: Move ontology GResource up ot the topmost .soCarlos Garnacho2020-09-012-1/+1
|/ | | | | | | This is being set on the internal .so file. This library is going static, so for the GResources to endure past our layers of linking, they must be set on a .so that will be ensured to be installed. That's libtracker-sparql itself.
* Merge branch 'wip/carlosg/release-memory' into 'master'Sam Thursfield2020-08-3110-0/+157
|\ | | | | | | | | Release memory on inactivity See merge request GNOME/tracker!306
| * libtracker-data: Plug reference leaksCarlos Garnacho2020-08-301-0/+6
| |
| * libtracker-data: Plug leakCarlos Garnacho2020-08-301-0/+12
| | | | | | | | | | The graph token was consistently being possibly leaked, if it had to be used again further on in the same query string.
| * libtracker-data: Plug leakCarlos Garnacho2020-08-301-0/+2
| |
| * libtracker-sparql/direct: Set up cleanup timeoutCarlos Garnacho2020-08-303-0/+76
| | | | | | | | | | | | This timeout checks every 30 seconds that the sparql connection has been inactive for some time, and triggers memory to be reclaimed in the update thread.
| * libtracker-data: Add internal API to release TrackerDataManager memoryCarlos Garnacho2020-08-306-0/+61
| | | | | | | | | | | | This call frees all inactive readonly TrackerDBInterfaces, and ensures that the readwrite one releases as much memory as possible (freeing all cached prepared statements, and asking SQLite to do so).
* | Merge branch 'wip/carlosg/sql-statements-debug' into 'master'Sam Thursfield2020-08-311-1/+32
|\ \ | | | | | | | | | | | | libtracker-data: Provide better sql-statements debug output See merge request GNOME/tracker!305
View Lorry Controller Status