Skip to content

sqlite / sqlcipher API inconsistency #150

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

Closed
alipov opened this issue Jan 7, 2015 · 4 comments
Closed

sqlite / sqlcipher API inconsistency #150

alipov opened this issue Jan 7, 2015 · 4 comments

Comments

@alipov
Copy link

alipov commented Jan 7, 2015

Hi,

Is there a reason why SQLiteStatement#executeUpdateDelete() 's return type is long, instead of int (as specified in Android's API)?

The value in any case comes from mDatabase.lastChangeCount(), which is int by itself, so I don't understand why to change the type. Could you please elaborate?

Thanks!
Alex.

@developernotes
Copy link
Member

Hello @alipov

Thank you for the inquiry, as it turns out, the call to lastChangeCount() internally calls SQLite sqlite3_changes which returns an int. This is likely a historical mistake, we will correct the return signature. Thanks!

@alipov
Copy link
Author

alipov commented Jul 8, 2015

Hi @developernotes

Half year passed and this issue not yet fixed.
Would you like me to open a pull request?

Alex.

@developernotes
Copy link
Member

Hello @alipov

Thank you for the reminder, I have made the change in the following commit.

@alipov
Copy link
Author

alipov commented Jul 9, 2015

Great, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants