Re: [sqlite] Datatypes (D. Richard Hipp)

6, 2009 12:23 PM To: General Discussion of SQLite Database Subject: Re: [sqlite] Datatypes (D. Richard Hipp) On 16 Jun 2009, at 5:32pm, Fred Williams wrote: > Still think, logically speaking, the construct should throw an error > message, rather than make stealth changes to the expected re

Re: [sqlite] Datatypes (D. Richard Hipp)

To: sqlite-users@sqlite.org Subject: Re: [sqlite] Datatypes (D. Richard Hipp) Fred Williams <f.willi...@verizon.net> wrote: > What! The standard is lacking? Will wonders never cease? > > Thanks, you saved me from some boring reference reading. > > Still think, logically sp

Re: [sqlite] Datatypes (D. Richard Hipp)

D. Richard Hipp wrote: > It was done to fix a bug. > > SQLite allows arbitrary text as the "datatype" of a column. So you > could say (for example): > > CREATE TABLE t1(a "duh! ++ x hi, yall!(+123)" unique); > > And the datatype for t1.a would be "duh! ++ x hi, yall!(+123)". It > used to

Re: [sqlite] Datatypes (D. Richard Hipp)

Fred Williams wrote: > What! The standard is lacking? Will wonders never cease? > > Thanks, you saved me from some boring reference reading. > > Still think, logically speaking, the construct should throw an error > message, rather than make stealth changes to the

Re: [sqlite] Datatypes (D. Richard Hipp)

On 16 Jun 2009, at 5:32pm, Fred Williams wrote: > Still think, logically speaking, the construct should throw an error > message, rather than make stealth changes to the expected result. I suppose it might be possible to provide SQLite with a 'conform to standard' mode you could select using

Re: [sqlite] Datatypes (D. Richard Hipp)

: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org]on Behalf Of Igor Tandetnik Sent: Tuesday, June 16, 2009 10:57 AM To: sqlite-users@sqlite.org Subject: Re: [sqlite] Datatypes (D. Richard Hipp) Fred Williams <f.willi...@verizon.net> wrote: > Is this a violation of SQL

Re: [sqlite] Datatypes (D. Richard Hipp)

users-boun...@sqlite.org]on Behalf Of D. Richard Hipp Sent: Tuesday, June 16, 2009 9:36 AM To: General Discussion of SQLite Database Subject: Re: [sqlite] Datatypes (D. Richard Hipp) > > > Ok, I can see this. But I cannot forsee the real implications > though. If I > have a statem

Re: [sqlite] Datatypes (D. Richard Hipp)

Fred Williams wrote: > Is this a violation of SQL Standards? Seems like it should be. As far as I can tell, CREATE TABLE AS SELECT is not part of SQL92 standard at all. If you want to work within the standard, don't use this construct in the first place. Igor

Re: [sqlite] Datatypes (D. Richard Hipp)

users-boun...@sqlite.org]on Behalf Of D. Richard Hipp Sent: Tuesday, June 16, 2009 9:36 AM To: General Discussion of SQLite Database Subject: Re: [sqlite] Datatypes (D. Richard Hipp) > > > Ok, I can see this. But I cannot forsee the real implications > though. If I > have a statem

Re: [sqlite] Datatypes (D. Richard Hipp)

> > > Ok, I can see this. But I cannot forsee the real implications > though. If I > have a statement like > > create table mytable(pnumber integer, name varchar(20), primary > key(pnumber)) > > what are the reported datatypes? still integer and varchar(20)? Yes. But if you do CREATE

Re: [sqlite] Datatypes (D. Richard Hipp)

On Jun 16, 2009, at 8:47 AM, A Drent wrote: > > From the docs I read that for the new version: > > a.. When new tables are created using CREATE TABLE ... AS SELECT ... > the > datatype of the columns is the simplified SQLite datatype (TEXT, > INT, REAL, > NUMERIC, or BLOB) instead of a copy of the