> For SQLite the integer can be up to 8 bytes and will casting as "INTEGER" solve the problem without overflow? You can ask the foremost expert yourself: sqlite. If it behaves that way today you can be 99.99% certain it will behave that way in 10 years (the project places tremendous value on backwards compatibility). ``` sqlite> select cast(4011110000001 as integer); 4011110000001 sqlite> select cast(401111000000100 as integer); 401111000000100 sqlite> select cast(4011110000001000 as integer); 4011110000001000 sqlite> select cast(40111100000010000 as integer); 40111100000010000 sqlite> select cast(401111000000100000 as integer); 401111000000100000 sqlite> select cast(4011110000001000000 as integer); 4011110000001000000 sqlite> select cast(40111100000010000000 as integer); 9223372036854775807 ```