diff options
author | Philip Van Hoof <philip@codeminded.be> | 2011-06-24 17:56:01 +0200 |
---|---|---|
committer | Jürg Billeter <j@bitron.ch> | 2011-06-29 17:24:42 +0200 |
commit | 79ad6802d34a8d2f45c2de7b760b2dabe10fbb29 (patch) | |
tree | 2c56abb32a6efabe2973c28dbcbbfbba504a50f0 /tests/libtracker-fts | |
parent | 44ca01c2fec4ae4c5fb38efe0f928e75a477188e (diff) | |
download | tracker-79ad6802d34a8d2f45c2de7b760b2dabe10fbb29.tar.gz |
libtracker-data: Initialization of db during restore must be handled if fails
In case the initialization of the db fails during the restore of a
backup, and only in case of --disable-journal, then should the init
fail with an error instead of trying to recreate a clean meta.db
Diffstat (limited to 'tests/libtracker-fts')
-rw-r--r-- | tests/libtracker-fts/tracker-fts-test.c | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/tests/libtracker-fts/tracker-fts-test.c b/tests/libtracker-fts/tracker-fts-test.c index 717d5a8ff..cb1dc5b4a 100644 --- a/tests/libtracker-fts/tracker-fts-test.c +++ b/tests/libtracker-fts/tracker-fts-test.c @@ -75,7 +75,8 @@ test_sparql_query (gconstpointer test_data) tracker_db_journal_set_rotating (FALSE, G_MAXSIZE, NULL); tracker_data_manager_init (TRACKER_DB_MANAGER_FORCE_REINDEX, test_schemas, - NULL, FALSE, 100, 100, NULL, NULL, NULL, &error); + NULL, FALSE, FALSE, + 100, 100, NULL, NULL, NULL, &error); g_assert_no_error (error); |