Revision 3300
Added by Aaron Marcuse-Kubitza over 12 years ago
| tree_cross-links.sql | ||
|---|---|---|
| 81 | 81 |
ALTER TABLE plantname_ancestor |
| 82 | 82 |
OWNER TO bien; |
| 83 | 83 |
|
| 84 |
-- Index: fki_plantname_ancestor_ancestor_id |
|
| 85 |
|
|
| 86 |
-- DROP INDEX fki_plantname_ancestor_ancestor_id; |
|
| 87 |
|
|
| 88 |
CREATE INDEX fki_plantname_ancestor_ancestor_id |
|
| 89 |
ON plantname_ancestor |
|
| 90 |
USING btree |
|
| 91 |
(ancestor_id ); |
|
| 92 |
|
|
| 93 |
-- Index: fki_plantname_ancestor_plantname_id |
|
| 94 |
|
|
| 95 |
-- DROP INDEX fki_plantname_ancestor_plantname_id; |
|
| 96 |
|
|
| 97 |
CREATE INDEX fki_plantname_ancestor_plantname_id |
|
| 98 |
ON plantname_ancestor |
|
| 99 |
USING btree |
|
| 100 |
(plantname_id ); |
|
| 101 |
|
|
| 102 | 84 |
----- Trigger |
| 103 | 85 |
|
| 104 | 86 |
-- Trigger: plantname_update_ancestors on plantname |
Also available in: Unified diff
schemas/tree_cross-links.sql: Ancestors table: Synced with current definition, which removes unneeded fki_* indexes. Note that the index on ancestor_id might be needed in the future if we ever want to get all the descendants of a plantname/namedplace or perform deletions on plantname/namedplace (which cascade to *_ancestor). For getting all the plantnames/namedplaces (of any rank) for a plantconcept/locationdetermination, though, the *_ancestor_pkey index is sufficient because plantname_id/namedplace_id is the first column in it.