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 be that this datatype would be copied into the synthesized > CREATE TABLE statements for tables generated using CREATE TABLE AS. > But that required that the datatype name be properly quoted so that it > could be parsed again. The logic that did this quoting was complex > and contained bugs. It was much easier to strip out the whole thing > and replace it with primitive datatype generator (that inserts "NUM" > in place of the complex string show above) than to try to fix the > quoting for every possible case. >
I agree that quoting a type like "duh! ++ x hi, yall!(+123)" would be a pain, and that this bug fix is mostly a good one. I worry though that in most cases no such quoting would be needed and that in some cases this bug fix will be represent a backwards- incompatible change. Would it be possible to pass through those type names which require no quoting (e.g., all alphanumeric type names, possibly alphanumeric type names with whitespace but no other special characters)? Nico -- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
