From 79ad6802d34a8d2f45c2de7b760b2dabe10fbb29 Mon Sep 17 00:00:00 2001 From: Philip Van Hoof Date: Fri, 24 Jun 2011 17:56:01 +0200 Subject: 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 --- tests/libtracker-fts/tracker-fts-test.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'tests/libtracker-fts') 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); -- cgit v1.2.1