New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why not use android.database.SQLException? #223

Closed
greenrobot opened this Issue Apr 5, 2016 · 1 comment

Comments

Projects
None yet
2 participants
@greenrobot

When switching from the system's SQLite to SQLCipher, one of the more obvious behavioral changes is exception handling. Apps that work with android.database.SQLException or one of its subclasses have to be changed. The compiler won't complain because those are runtime exceptions.

That's why I wanted to ask if SQLCipher could use the standard exceptions for better compatibility. The standard constructors are public: http://developer.android.com/intl/in/reference/android/database/sqlite/SQLiteException.html

@developernotes

This comment has been minimized.

Show comment
Hide comment
@developernotes

developernotes Apr 5, 2016

Member

Hello @greenrobot

Thank you for your feedback. The inclusion of SQLiteException found within the Java API is historical, as the project was initially assembled from an currently dated version of android.database.sqlite. We will keep this in mind as we make changes to support Android N going forward.

Member

developernotes commented Apr 5, 2016

Hello @greenrobot

Thank you for your feedback. The inclusion of SQLiteException found within the Java API is historical, as the project was initially assembled from an currently dated version of android.database.sqlite. We will keep this in mind as we make changes to support Android N going forward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment