Re: [sqlite] data type problem

but if you create a table using: CREATE TABLE XTollData ( DutyID char (32) NOT NULL , CarNumber char (10) NULL ); SQLite3_Column_decltype will return the result of 'DutyID' as 'char(32)'. That is, SQLite3_Column_decltype treat '[char](32)' as 'char', treat 'char(32)' as 'char(32)'. I

[sqlite] Different IN behavior from 3.2.x to 3.3.x

Try this with an old 3.2.x sqlite version SQLite version 3.2.8 Enter ".help" for instructions sqlite> CREATE Table test (a, b, c); sqlite> INSERT into test (a,b,c) VALUES ('1', '2', '3'); sqlite> SELECT * FROM test WHERE a||b||c = '123'; 1|2|3 sqlite> SELECT * FROM test WHERE a||b||c IN ('123');

Re: [sqlite] Different IN behavior from 3.2.x to 3.3.x

Paolo Vernazza <[EMAIL PROTECTED]> wrote: > Try this with an old 3.2.x sqlite version > > SQLite version 3.2.8 > Enter ".help" for instructions > sqlite> CREATE Table test (a, b, c); > sqlite> INSERT into test (a,b,c) VALUES ('1', '2', '3'); > sqlite> SELECT * FROM test WHERE a||b||c = '123'; >

Re: [sqlite] data type problem

[EMAIL PROTECTED] wrote: > but if you create a table using: > > CREATE TABLE XTollData ( > DutyID char (32) NOT NULL , > CarNumber char (10) NULL > ); > > SQLite3_Column_decltype will return the result of 'DutyID' as 'char(32)'. > That is, SQLite3_Column_decltype treat '[char](32)' as

Re: [sqlite] data type problem

[EMAIL PROTECTED] wrote: > but if you create a table using: > > CREATE TABLE XTollData ( > DutyID char (32) NOT NULL , > CarNumber char (10) NULL > ); > > SQLite3_Column_decltype will return the result of 'DutyID' as 'char(32)'. > That is, SQLite3_Column_decltype treat '[char](32)' as

[sqlite] beginner's questions: atexit problem

Hello, I would like to try SQLite database, but I am not able to compile quickstart example. Using dev-c++ 4.9.9.2-wx-beta-6.8 with mingw 3.4.2 I have got the error: sqlite3.A(.text+0x44):fake: multiple definition of `atexit' C:/../lib/gcc/mingw32/3.4.2/../../../crt2.o(.text+0x260):crt1.c:

Re: [sqlite] beginner's questions: atexit problem

Are you mixing Cygwin and MinGW libraries and/or header files? --- timm2 <[EMAIL PROTECTED]> wrote: > Using dev-c++ 4.9.9.2-wx-beta-6.8 with mingw 3.4.2 I have got the error: > > sqlite3.A(.text+0x44):fake: multiple definition of `atexit' >

[sqlite] Index creation on huge table will never finish.

Hi all, I have a very simple schema. I need to assign a unique identifier to a large collection of strings, each at most 80-bytes, although typically shorter. The problem is I have 112 million of them. My schema looks as follows: CREATE TABLE rawfen ( fen VARCHAR(80) ); CREATE INDEX

Re: [sqlite] Index creation on huge table will never finish.

On 3/21/07, Chris Jones <[EMAIL PROTECTED]> wrote: Hi all, I have a very simple schema. I need to assign a unique identifier to a large collection of strings, each at most 80-bytes, although typically shorter. The problem is I have 112 million of them. My schema looks as follows: CREATE

Re: [sqlite] Index creation on huge table will never finish.

I don't think that solves my problem. Sure, it guarantees that the IDs are unique, but not the strings. My whole goal is to be able to create a unique identifier for each string, in such a way that I dont have the same string listed twice, with different identifiers. In your solution, there

Re: [sqlite] Index creation on huge table will never finish.

You stated in your OP I need to assign a unique identifier to a large collection of strings Obviously I misunderstood that to mean you wanted the strings tagged uniquely, not that the strings were unique. In your case, it seems then, you will have to put up with checking each string, and as

Re: [sqlite] Index creation on huge table will never finish.

Chris Jones wrote: Hi all, I have a very simple schema. I need to assign a unique identifier to a large collection of strings, each at most 80-bytes, although typically shorter. The problem is I have 112 million of them. Maybe you could start by breaking the data into 8 equal groups and