Re: [sqlite] BigInt loss accuracy

2019-02-25 Thread David Raymond
te-users-boun...@mailinglists.sqlite.org] On Behalf Of Derek Wang Sent: Saturday, February 23, 2019 1:49 PM To: sqlite-users@mailinglists.sqlite.org Subject: [sqlite] BigInt loss accuracy sqlite biggest int is supposedly 9,223,372,036,854,775,807 (9 and a bit Quintillion), but when the number is lar

Re: [sqlite] BigInt loss accuracy

2019-02-23 Thread Clemens Ladisch
Derek Wang wrote: > sqlite biggest int is supposedly 9,223,372,036,854,775,807 (9 and a bit > Quintillion), but when the number is larger than 1E+17, it loses some > accuracy when retrieving. In plain SQL, everything works fine up to the limit: create table t(i notoriously big integer); with

Re: [sqlite] BigInt loss accuracy

2019-02-23 Thread Igor Tandetnik
On 2/23/2019 1:48 PM, Derek Wang wrote: x = 10 for i in range(22): x = 10*x y = x + 3 s = 'insert into bi values (%s, %s, %s)' % (i, y, y) Print `s`. I suspect you are losing precision on Python side, during text formatting. -- Igor Tandetnik ___

[sqlite] BigInt loss accuracy

2019-02-23 Thread Derek Wang
sqlite biggest int is supposedly 9,223,372,036,854,775,807 (9 and a bit Quintillion), but when the number is larger than 1E+17, it loses some accuracy when retrieving. see the following python codes: #store into sqlite: import sqlite3 sql_1 = """ CREATE TABLE IF NOT EXISTS bi (i integer,bi big