On 16/06/2009 10:47 PM, A Drent wrote: > Sorry, something went wrong on the previous post.
*AND* on this one; you are starting a new topic but you included about 900 lines from today's digest!! >>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 original datatype from the source > table. What source table? There may be 0, 1, or many tables involved. E.g. create table foo as select 1, 2.34, 'hello', x'f00baa', null; > I don't know why this has been done, as far as I can tell this will cause > trouble in several wrappers. I.e. the Delphi wrappers depend on regular > datatypes like varchar(xx), number etc. If SQLite will 'translate' this into > other datatypes this will cause inconsistancies. If this is necessary why > not then just allow the primitive datatypes within the 'create'? Then the > reported datatype will be the same as the datatypes uses within the create. > What will happen on a create table when the datatype is other then the > primitives? How does SQLite translate these? Or am I completely > misundertanding things? Possibly. To save us from misunderstanding you, show us a concrete example of something going wrong (in your opinion). > > albert [BIG SNIP] _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
