summaryrefslogtreecommitdiff
path: root/client/changes/feature_use-twisted-adbapi-for-sync-db
diff options
context:
space:
mode:
authordrebs <drebs@leap.se>2015-05-04 13:04:56 -0300
committerdrebs <drebs@leap.se>2015-05-20 10:16:46 -0300
commit3a7ddacd06fd57afb10cc3d7083c2aa196c9328f (patch)
tree7c5dbb40a7f01e087101df08d7824afbd8abc27b /client/changes/feature_use-twisted-adbapi-for-sync-db
parentb75bedb065cfbbb2993659d867ef554ff70596ae (diff)
[feature] use async adbapi for async decryption
Since we started implementing twisted api in soledad, some pieces are missing. Accessing the sqlcipher database directly with the twisted adbapi facilities is one of them. The async encryption/decryption was touching the database directly, and this was causing some difficulties like having different threads accessing the same database. This commit implements the twisted adbapi stuff for the asynchronous encryption/decryption facilities. Next steps would be use async adbapi for async encryption and use async adbapi for all sqlcipher access.
Diffstat (limited to 'client/changes/feature_use-twisted-adbapi-for-sync-db')
-rw-r--r--client/changes/feature_use-twisted-adbapi-for-sync-db1
1 files changed, 1 insertions, 0 deletions
diff --git a/client/changes/feature_use-twisted-adbapi-for-sync-db b/client/changes/feature_use-twisted-adbapi-for-sync-db
new file mode 100644
index 00000000..41e5e6e3
--- /dev/null
+++ b/client/changes/feature_use-twisted-adbapi-for-sync-db
@@ -0,0 +1 @@
+ o Use twisted.enterprise.adbapi for access to the sync database.