Fixed an issue related to multiple database connection
authorJihoon Chung <jihoon.chung@samsaung.com>
Sat, 17 Aug 2013 06:01:15 +0000 (15:01 +0900)
committerSoo-Hyun Choi <sh9.choi@samsung.com>
Sun, 18 Aug 2013 06:59:02 +0000 (15:59 +0900)
commite98b3570bdcf1b2b7772fb8450bbf66f3ddf029f
treed304627f5093da9f320e34b450fffe0c4d3f4809
parent984e08f8b19ef64cc3faf7fc6745aceface37f61
Fixed an issue related to multiple database connection

- As every web application has its own security dao,
  support of multiple DB connections will not be needed.

[Issue#]   N/A
[Problem]  Setting menu shows wrong information with the following steps.
           1. Launch Setting -> Manage applications
           2. Select Web application -> Allow list
           3. Back to Manage applications -> select another Web application
           4. checking Allow list menu
           then, the menu showed the firstly chosen web application information.
[Cause]    Security origin dao is not released even though corresponding dao object is released.
           This causes returning old data when a new dao object is created.
           N.B) Security origin dao uses static value to avoid
                conflict with re-created connection object.
[Solution] Remove static dao value, and clen up old dao code.
           - We originally needed "static value" to support thread locking mechanism.
             But, current web applications don't have separate threads, hence no longer needed.
           - Moreover, sqlite already supports such a conflict through transaction manager.
[SCMRequest] N/A

Change-Id: Ide83f7c8fa63a387e48f0396c3a8febc79409101
modules/security_origin_dao/CMakeLists.txt
modules/security_origin_dao/dao/security_origin_dao.cpp
modules/security_origin_dao/dao/security_origin_database.cpp [deleted file]
modules/security_origin_dao/include/wrt-commons/security-origin-dao/security_origin_dao.h [changed mode: 0755->0644]
modules/security_origin_dao/include/wrt-commons/security-origin-dao/security_origin_database.h [deleted file]