> ...which actually surprises me, since I was under the impression > CREATE TABLE ... AS SELECT always produced NONE affinities. Is this > a semi-recent (last year) change?
It looks like the only recent change was a year ago: http://www.sqlite.org/changes.html#version_3_6_15. But according to release notes even before that column affinities should have been preserved... Pavel On Tue, Jun 29, 2010 at 9:46 AM, Jay A. Kreibich <j...@kreibi.ch> wrote: > On Tue, Jun 29, 2010 at 06:59:18AM -0400, Tim Romano scratched on the wall: >> CREATE TABLE "main"."proto" ("id" INTEGER PRIMARY KEY AUTOINCREMENT NOT >> NULL , "name" TEXT) >> CREATE TABLE "main"."clone" as select * from PROTO >> >> The primary key of table CLONE is defined as "INT" not "INTEGER". > > The only information preserved by CREATE TABLE ... AS SELECT is the > column affinity (not "type"). These are equivalent, and both > translate to an INTEGER affinity. > > > > ...which actually surprises me, since I was under the impression > CREATE TABLE ... AS SELECT always produced NONE affinities. Is this > a semi-recent (last year) change? > > -j > > > -- > Jay A. Kreibich < J A Y @ K R E I B I.C H > > > "Intelligence is like underwear: it is important that you have it, > but showing it to the wrong people has the tendency to make them > feel uncomfortable." -- Angela Johnson > _______________________________________________ > 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
