Revision 5656
Added by Aaron Marcuse-Kubitza about 12 years ago
| vegbien.my.sql | ||
|---|---|---|
| 227 | 227 |
parent_id int(11), |
| 228 | 228 |
taxonepithet text, |
| 229 | 229 |
rank text, |
| 230 |
identifyingtaxonomicname text,
|
|
| 230 |
taxonomicname text, |
|
| 231 | 231 |
accessioncode text |
| 232 | 232 |
); |
| 233 | 233 |
|
| ... | ... | |
| 303 | 303 |
|
| 304 | 304 |
|
| 305 | 305 |
-- |
| 306 |
-- Name: COLUMN taxonlabel.identifyingtaxonomicname; Type: COMMENT; Schema: public; Owner: -
|
|
| 306 |
-- Name: COLUMN taxonlabel.taxonomicname; Type: COMMENT; Schema: public; Owner: - |
|
| 307 | 307 |
-- |
| 308 | 308 |
|
| 309 | 309 |
|
Also available in: Unified diff
schemas/vegbien.sql: taxonlabel: Renamed identifyingtaxonomicname to taxonomicname because the taxonomicname provided by the datasource is now in taxonverbatim, so there is no name collision. Note that both of these fields store the same type of information, but taxonlabel's is autogenerated while taxonverbatim's is verbatim (and is only set if provided by the datasource).