>> Brickl Roland [mailto:[EMAIL PROTECTED] wrote:
>> Integer PrimaryKeys are always autoincrementing. When you don't
>> specify it it uses after (2^63)-1 a random free positiv value.
>> "Odekirk, Shawn" <[EMAIL PROTECTED]> wrote:
>> I will compile this for Windows and see what my results are
Brickl Roland [mailto:[EMAIL PROTECTED] wrote:
> Integer PrimaryKeys are always autoincrementing. When you don't
> specify it it uses after (2^63)-1 a random free positiv value.
"Odekirk, Shawn" <[EMAIL PROTECTED]> wrote:
> I will compile this for Windows and see what my results are using a
>
"Odekirk, Shawn" <[EMAIL PROTECTED]> wrote:
> My compiler is old and I don't think it supports a 64 bit data type.
> Maybe this is the root cause of my problem.
>
Very likely.
--
D. Richard Hipp <[EMAIL PROTECTED]>
ubject: RE: [sqlite] INTEGER PRIMARY KEY Auto Increment Rollover
Question
Hallo Odekirk Shawn,
SQLite use up to an 64Bit signed Integer for Primary Keys, even on non
64Bit-Systems!
Integer PrimaryKeys are always autoincrementing. When you don't specify
it it uses after (2^63)-1
a random free positiv value
Hallo Odekirk Shawn,
SQLite use up to an 64Bit signed Integer for Primary Keys, even on non
64Bit-Systems!
Integer PrimaryKeys are always autoincrementing. When you don't specify it it
uses after (2^63)-1
a random free positiv value. When you write autoincrement for your create table
it never
I am evaluating SQLite for a project I am working on.
I have a question about the behavior of the INTEGER PRIMARY KEY auto
increment feature.
My platform uses 32 bit integers, so the valid values for an unsigned
integer are 0 - 4294967296 and the valid values for a signed integer are
-2147483648
6 matches
Mail list logo