diff options
| author | Carlos Garnacho <carlosg@gnome.org> | 2021-03-20 11:18:25 +0100 |
|---|---|---|
| committer | Carlos Garnacho <carlosg@gnome.org> | 2021-03-26 12:20:58 +0100 |
| commit | 2d0c0cb01876f35297741846182a2048b76df516 (patch) | |
| tree | c7e2c0e65fcd92c08536052c4f00078a13391914 | |
| parent | aa3caa512bd99bac485d110b4a06cc3d9dbecf83 (diff) | |
| download | tracker-2d0c0cb01876f35297741846182a2048b76df516.tar.gz | |
libtracker-data: Add paranoia check in condition
According to Coverity, there's weird paths that may cause an ontology
change on a new class that may still result on us trying to update the
range of a related property.
It remains to be seen whether the combination of circumstances that
lead to this can ever happen together, but it's simple enought to add
the paranoia check as those variables where we are composing the ALTER
TABLE would be actually empty.
CID: #1501144
| -rw-r--r-- | src/libtracker-data/tracker-data-manager.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/libtracker-data/tracker-data-manager.c b/src/libtracker-data/tracker-data-manager.c index 67f97e687..8094da2ae 100644 --- a/src/libtracker-data/tracker-data-manager.c +++ b/src/libtracker-data/tracker-data-manager.c @@ -2951,7 +2951,7 @@ create_decomposed_metadata_tables (TrackerDataManager *manager, put_change = TRUE; } - if (in_change && put_change) { + if (in_change && put_change && in_col_sql && sel_col_sql) { range_change_for (property, in_col_sql, sel_col_sql, field_name); } } |