Revision 4702
Added by Aaron Marcuse-Kubitza about 12 years ago
| vegbien.sql | ||
|---|---|---|
| 945 | 945 |
|
| 946 | 946 |
|
| 947 | 947 |
-- |
| 948 |
-- Name: TABLE plantname; Type: COMMENT; Schema: public; Owner: - |
|
| 949 |
-- |
|
| 950 |
|
|
| 951 |
COMMENT ON TABLE plantname IS 'To include a taxon name at a rank with no explicit column, create a plantname for it and point to it using plantname_id. To include multiple such names, chain the plantnames together using parent_id, as a form of ordered linked list. Note that lower-level taxa should point to higher-level taxa.'; |
|
| 952 |
|
|
| 953 |
|
|
| 954 |
-- |
|
| 948 | 955 |
-- Name: COLUMN plantname.rank; Type: COMMENT; Schema: public; Owner: - |
| 949 | 956 |
-- |
| 950 | 957 |
|
Also available in: Unified diff
schemas/vegbien.sql: plantname: Added comment documenting how to include a taxon name at a rank with no explicit column, by using the plantname table as an ordered linked list linked together using parent_id. (This method of using a linked list is one way of storing an ordered list of user-defined data. It is similar to using locationevent.previous_id to link successive reobservations of the same location together.) Note that plantname can store both the official tree of life and the data provider's own custom tree of life (or a subset thereof), with the two being distinguished by whether the data provider's or TNRS's taxondeterminations point to them.