This question is locked. New answers and comments are not allowed.
Hello
I have a UNSIGNED BIG INT field in my database, and entry does not get saved properly. It looks like an overflow (I am saving a timestamp (time in ms) and when I read it out I get a negative number).
However, that only happens on my Andriod 4.2 test device. In Simulator it works fine and also on other 2.3 Andriod device it works just fine. My 4.2 device is up to date.
I can overcome it by saving timestamp as string, but I really need to use big int, because it saves me from a lot of conversion issues later on.
Thanks
I have a UNSIGNED BIG INT field in my database, and entry does not get saved properly. It looks like an overflow (I am saving a timestamp (time in ms) and when I read it out I get a negative number).
However, that only happens on my Andriod 4.2 test device. In Simulator it works fine and also on other 2.3 Andriod device it works just fine. My 4.2 device is up to date.
I can overcome it by saving timestamp as string, but I really need to use big int, because it saves me from a lot of conversion issues later on.
Thanks
1 Answer, 1 is accepted
0
David Silveria
Top achievements
Rank 1
Rank 1
answered on 05 Sep 2013, 01:55 PM
Cannot really give you a solution/advise, but according to your description, it sounds like a bug in the Sqlite version for Android 4.2. Sqlite versions are updated frequently with each Android upper version, but also some device manufacturers swap their own choice of sqlite in their phones. Check this link: http://stackoverflow.com/a/4377116/1854553
Cheers!
Cheers!