[prev] [thread] [next] [lurker] [Date index for 2005/05/25]
> SQLite trys to promote whatever goes in to be a number. Despite claiming > that it won't IIRC, SQLite doesn't really do data types. Sure your Perl wrapper isn't doing something horrid to you? My current problem with SQLite, for example, is in its Tcl binding. The underlying code can do what I want, but it's not exposed to the Tcl code. > http://www.sqlite.org/datatype3.html From my reading of this page, if you do INSERT INTO foo VALUES('1.0',1.0); then the first will be TEXT, the second NUMERIC. If you're using quotes selectively (for example, just to quote strings for security), then your version number will go in as an integer. Column affinity may THEN turn it back into another data type. Thanks for bringing this up, my code currently quotes everything, and I'll have to leave integers unquoted if I switch to SQLite.
Generated at 04:00 on 26 May 2005 by mariachi 0.52