I am designing a database for carbon modeling. Many of the parameters to be stored in the db have very long names... it is kinda inconvenient to have column names such as 'new_live_wood_Carbon_to_new_total_wood_Carbon', but I hate column names such as 'nlivwdc2ntotwdc'. I may as well just call that column 'a' and then have a lookup table which describes 'a' => 'Ratio of new live wood Carbon to new total wood Carbon' along with possibly other descriptors (some columns are a flag, that is, 0 or 1, while others are integers or fractions, and so on).
Any suggestions on how to embed this metadata in the table? Is the following the best way -- CREATE TABLE foo ( a REAL, -- Ratio of new live wood Carbon to new total wood Carbon b INTEGER -- (minimum interval between disturbances) ); And, how do I store metadata about the table itself? The following doesn't stick in the schema -- -- The table 'foo' is blah blah CREATE TABLE foo (); -- Puneet Kishor http://www.punkish.org/ Nelson Institute for Environmental Studies http://www.nelson.wisc.edu/ Carbon Model http://carbonmodel.org/ Open Source Geospatial Foundation http://www.osgeo.org/ _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
