projects / platform / core / security / key-manager.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 2c86e0b) | patch
Add backend id to database scheme 87/39487/5
authorKrzysztof Jackiewicz <k.jackiewicz@samsung.com>
Fri, 15 May 2015 09:59:27 +0000 (11:59 +0200)
committerBartlomiej Grzelewski <b.grzelewski@samsung.com>
Tue, 19 May 2015 08:21:59 +0000 (01:21 -0700)
commit94cd4b238acc09261439071cf5e7a9be114eee93
treebaba930d1411224f4fa6efffcaca71d809abbe39tree | snapshot
parent2c86e0b2cd70a09169c59bba5c4e45cc670a4a36commit | diff
Add backend id to database scheme

[Issue#] N/A
[Feature/Bug] N/A
[Problem] N/A
[Cause] We have to keep backend id in database.
[Solution] Schema updated

[Verification] Run migration tests:
ckm-tests-internal --run_test=DBCRYPTO_MIGRATION_TEST
ckm-tests-internal --run_test=DBCRYPTO_TEST/DBtestBackend

Change-Id: Ib33d6c360d655f7c7a01164385e284ec8f759837
data/scripts/create_schema.sql diff | blob | history
data/scripts/migrate_3.sql [new file with mode: 0644] blob
packaging/key-manager.spec diff | blob | history
src/manager/service/db-crypto.cpp diff | blob | history
tests/DBFixture.cpp diff | blob | history
tests/main.cpp diff | blob | history
tests/test_db_crypto.cpp diff | blob | history
tests/testme_ver3.db [new file with mode: 0644] blob
Domain: Security / Utilities;