Is this a violation of SQL Standards? Seems like it should be. I'm not for dumbing down the system to compensate for the occasional idiot programmer. After all, we are not the government, nor should we strive to act like it (IMHO).
If someone chooses to attempt to create a column/table/database name that is incorrect perhaps they should receive a refreshing error message pointing out their verbal shortcomings? Otherwise I think this could break a lot of good code for the sake of "maybe"... Fred -----Original Message----- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-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 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 TABLE t2 AS SELECT * FROM mytable; Then the reported datatypes for t2 will be INT and TEXT. D. Richard Hipp d...@hwaci.com _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
