This approach: CREATE TABLE blob_table ( ModelNo TEXT, SerialNo TEXT, VSWR BLOB_DOUBLE )
involves comments? I don't see how. Nothing wrong with the comments approach, but this is an approach that just takes advantage of the fact that SQLite does not have fixed data types. Eric From: Simon Slavin<mailto:slav...@bigfraud.org> Sent: ?Saturday?, ?May? ?9?, ?2015 ?3?:?52? ?PM To: General Discussion of SQLite Database<mailto:sqlite-users at mailinglists.sqlite.org> On 9 May 2015, at 8:12pm, Drago, William @ CSG - NARDA-MITEQ <William.Drago at L-3com.com> wrote: > Best idea yet! Anyone see any issues with this? It's actually a comment, and SQLite provides ways of putting proper comments in table definitions: CREATE TABLE blob_table ( ModelNo TEXT, -- new-style models as used from 2006 onwards SerialNo TEXT, VSWR BLOB -- array of ten double-length floats ) These comments can be found if you look at the table definition in sqlite_master. I've also seen SQL databases where the designer created an otherwise unused table to hold comments on every column, something like this: CREATE TABLE _structure ( tableName TEXT, columnName TEXT, introduced TEXT, variableType TEXT, theComments TEXT ) 'introduced' was the edit of their program which first used the column (equivalent to 'checkin' as used by the SQLite development team). 'variableType' was not the SQL type but the type of variable in the programming language they were using the database with. This helped because the language had numerous variable types and subtle bugs could be introduced if you, for example, stored a value from an unsigned integer then did maths on the value in a long integer. Simon. _______________________________________________ sqlite-users mailing list sqlite-users at mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
