You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This plugin version does have a workaround to avoid a memory issue with extra-large result sets on Android, as already discussed in storesafe/cordova-sqlite-storage-help#70, and I have an organization who is interested in using a similar solution together with SQLCipher. They would like to start testing this kind of a solution within the next 1-2 weeks if possible.
The challenge is that the existing workaround solution was designed to work with the evplus NDK build and not with the standard android.database API which is supported by sqlcipher/android-database-sqlcipher.
The organization's timelines would preclude making a new evplus NDK build with SQLCIpher. A new evplus NDK build with SQLCipher would need to include a build of OpenSSL as well, like they made in sqlcipher/android-database-sqlcipher.
This means that we would need an evplus enhancement with a similar memory workaround solution working with the android.database API, as generally configured by the androidDatabaseProvider: 'system' setting.
I would very likely make this kind of enhancement on this plugin version and then use it to make the new evplus plugin for SQLCipher.
P.S. I am raising this issue due to the urgency for the organization. I have already started working on a new SQLite plugin design, as discussed in brodycj/ask-me-anything#3, which would much rather support in the long run.
The text was updated successfully, but these errors were encountered:
This plugin version does have a workaround to avoid a memory issue with extra-large result sets on Android, as already discussed in storesafe/cordova-sqlite-storage-help#70, and I have an organization who is interested in using a similar solution together with SQLCipher. They would like to start testing this kind of a solution within the next 1-2 weeks if possible.
The challenge is that the existing workaround solution was designed to work with the evplus NDK build and not with the standard android.database API which is supported by
sqlcipher/android-database-sqlcipher
.The organization's timelines would preclude making a new evplus NDK build with SQLCIpher. A new evplus NDK build with SQLCipher would need to include a build of OpenSSL as well, like they made in
sqlcipher/android-database-sqlcipher
.This means that we would need an evplus enhancement with a similar memory workaround solution working with the android.database API, as generally configured by the
androidDatabaseProvider: 'system'
setting.I would very likely make this kind of enhancement on this plugin version and then use it to make the new evplus plugin for SQLCipher.
P.S. I am raising this issue due to the urgency for the organization. I have already started working on a new SQLite plugin design, as discussed in brodycj/ask-me-anything#3, which would much rather support in the long run.
The text was updated successfully, but these errors were encountered: