Heart: Remove the mechanism which removes logging-data from Heart DB by explict data... 53/130953/1
authorKunhoon Baik <knhoon.baik@samsung.com>
Wed, 24 May 2017 12:45:00 +0000 (21:45 +0900)
committerKunhoon Baik <knhoon.baik@samsung.com>
Wed, 24 May 2017 12:45:00 +0000 (21:45 +0900)
commit6e584a17c9ddfa8a53b2900a7ce534d1f6b2b93d
treec94dbf22f24f9b937f979ba65835d2fcae502330
parentc9058f2d0c5ca8c1eb4dea2ce5b8d1daeade5403
Heart: Remove the mechanism which removes logging-data from Heart DB by explict data-query

In Tizen 3.0 and Early Tizen 4.0, we observed whether there are some requirements for deleting logging-data explictly.

Meanwhile, the logging functions like logging_get_latest_in_cache,logging_read_foreach has been used for several purposes.
However, there are some bugs that the logging functions do not consider such deleting data cache entries in module cache.
Thus, our plan was to improve the functions if there are some requirement for deleting logging-data explictly.

However, there are no requirements about it.
Thus, finally, we decided to remove the explict logging-data removing mechanism because there are no use cases.

Thus, from now, data of heart DBs will be removed according to just impliict(internal) rule.
That is, in this time, the old data is removed automatically when the DB size limit is reached.

Change-Id: Ief4cf1baa595030fddd6becd929165ee4857e8bb
src/heart/heart-storage.c
src/heart/include/logging.h
src/heart/logging.c