SqlLite Unsigned Big Int Overflow on Android 4.2

2 posts, 0 answers
  1. Filip
    Filip avatar
    35 posts
    Member since:
    Jul 2013

    Posted 05 Sep 2013 Link to this post


    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.


  2. David Silveria
    David Silveria avatar
    234 posts
    Member since:
    May 2006

    Posted 05 Sep 2013 Link to this post

    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

Back to Top