Forum Discussion
ODBC SQLite3: Large integers are truncated to Int32
Hello Maggie v-juanli-msft ,
thank you for taking the time!
You are correct to mention that the numbers in the SQLite3 database are used as ids, not for calculation - but unfortunately I cannot modify the SQLite3 database, because it is created by a third-party application (Anki with a defined database format). The numbers / ids are actually Unix epoch timestamps in milliseconds (factor 1000 !), so nowadays we are at roughly 1.5e12 (therefore 13 digits). Therefore the number "214..." only appears in Power BI and is not an id number in SQLite3.
Now I have tried to create a minimal SQLite3 database to reproduce the issue: Link
The table 'cards' contains 2 lines with the 13 digits ids:
In Power BI, after Get Data / ODBC / SQLite3 / database=(...)BIGINT-Test.anki2 / Default Credentials / Connect, I get
Maybe you can reproduce the issue?
Regards, Stephan.
Hello markvs , evandroportugal ,
it seems that in the thread Sqlite - Wrong integer imports in the Power BI community last year you had a similar issue like the one I am facing now: Large integer values are not imported correctly from SQLite3 to Power BI. As your thread does not contain an Accepted Solution: Have you been able to solve your problem otherwise or could you give me any hints on my issue? Any support would be appreciated...
Regards, Stephan.