Re: [sqlite] "bad" SQL runs on CREATE

2006-02-16 Thread Kiel W
On 2/16/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > SQLite, by design, accepts any data type. Even those you > might not have heard of before. This is a feature, not a > bug. It seems odd that a data type could be multiple words, but hey, that's just me. hmm, ok. Well no complaints if tha

Re: [sqlite] "bad" SQL runs on CREATE

2006-02-16 Thread drh
Dave Dyer <[EMAIL PROTECTED]> wrote: > > > >SQLite thinks you have declared a column named "active" > >with a datatype of "BOOL JOINED DATE". > > Since BOOL JOINED DATE doesn't correspond to any known > data type, shouldn't it be flagged as an error? Surely > the declaration of a table shouldn't

Re: [sqlite] "bad" SQL runs on CREATE

2006-02-16 Thread drh
Kiel W <[EMAIL PROTECTED]> wrote: > In version: 3.3.1 > > The following SQL runs fine without any errors: > > CREATE TABLE lnk_assoc_person ( > assoc TEXT, > person TEXT, > active BOOL > joined DATE, > left DATE > ); > > Notice the lack of a comma behind 'active B

[sqlite] "bad" SQL runs on CREATE

2006-02-16 Thread Kiel W
In version: 3.3.1 The following SQL runs fine without any errors: CREATE TABLE lnk_assoc_person ( assoc TEXT, person TEXT, active BOOL joined DATE, left DATE ); Notice the lack of a comma behind 'active BOOl'. Is this considered a bug or expected behavior? It is