Actually, what did was create a text file including :
CREATE TABLE [ART] ([artnr] INTEGER NOT NULL);
CREATE UNIQUE INDEX [IDX_ART] ON [ART]([artnr] ASC);
INSERT INTO "ART" VALUES('0000000001');
INSERT INTO "ART" VALUES('0000000002');
Etc.and then ran "sqlite3.exe my.db < my.sql" on the command line.
Using the windows version of the command line utility.
Worked fine until the numbers got out of 32-bit range. Not sure how, I
could try to use
unquoted integer values without the leading zeroes though - maybe that
works. It was just
a quick hack since the field values were originally string values.
Nick Shaw schrieb:
> As Igor says, it's most likely the way you're creating your SQL query.
> For example, if you're using C/C++ and you're trying to write a 64 bit
> number to a string using the %d flag in sprintf(), if won't work
> properly - you'd need to use %I64d for 64 bit numbers.
>
> 32-bit integers go up to (unsigned) 4,294,967,296, or (signed)
> +/-2,147,483,648 - any higher and it's a 64 bit number.
>
> For info, 64 bit integers go up to (unsigned) 18,446,744,073,709,551,616
> (20 digits) or (signed) +/-9,223,372,036,854,775,808 (19 digits).
>
> Thanks,
> Nick.
>
>
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
