integer overflow

[narychen]

The sqlite integer value should stored in 1, 2, 3, 4, 6, or 8 bytes depending on the magnitude of the value.
But on android, I tried two of my android phones
create table bbb (b integer)
insert into bbb(b) values (1458743338878) // time millisecond
select * from bbb

It turns out b = -1545541762
I change the type integer to int int8 bigint and it is always the same result. unless I use real.
I'm not sure the problem related to this driver. But on ios it has no problem.

[narychen]

I check my sqlite version with 'select sqlite_version()'
It's 3.7.11

[andpor]

Did you try to debug the Android module and see what comes out of the db call?

[narychen]

I'm sorry but I dont know which android method to start debug with.
Could you tell me the code related to this function so I could use android studio to see the values come out.

[narychen]

I think it could be the problem as the result comes out as a java int type. It's only 4 bytes.

[andpor]

You can start here:
public void executeSqlBatch(ReadableMap args, Callback success, Callback error)

[andpor]

Did you try both pure java and native Android implementations ?

[narychen]

Yes, both android and android-native implementation I tried have this problem

[andpor]

Android impl always fetches values for colums of INT type as long....

[andpor]

i found something...maybe it will fix the issue...i should be able to commit it soon..

[andpor]

Can you check the pure Java implementation? I adjusted some conversions...pull latest from this repo.

[narychen]

I've tried it. It fixed the problem. Really Awesome!

[andpor]

Great. I also updated native impl now.

[narychen]

Just one more question, should I use native impl in production environment or both impl will be ok?

[andpor]

both fully working. Your choice.

[andpor]

Fixed in 2.1.5

[kestasb]

Problem reappeared on Android devices in v3.3.5, though v3.3.4 is working fine.

[andpor]

yes, i spotted the issue. I will fix it and release 3.3.6 tomorrow - thanks for reporting..

[andpor]

fixed and released - please check it.