Revision 11147
Added by Aaron Marcuse-Kubitza about 11 years ago
vegbien.my.sql | ||
---|---|---|
429 | 429 |
|
430 | 430 |
|
431 | 431 |
-- |
432 |
-- Name: locationevent__pull_forward_from_parent(); Type: FUNCTION; Schema: public; Owner: - |
|
433 |
-- |
|
434 |
|
|
435 |
|
|
436 |
|
|
437 |
|
|
438 |
-- |
|
439 |
-- Name: FUNCTION locationevent__pull_forward_from_parent(); Type: COMMENT; Schema: public; Owner: - |
|
440 |
-- |
|
441 |
|
|
442 |
|
|
443 |
|
|
444 |
|
|
445 |
-- |
|
432 | 446 |
-- Name: make_family_higher_plant_group(); Type: FUNCTION; Schema: public; Owner: - |
433 | 447 |
-- |
434 | 448 |
|
... | ... | |
6143 | 6157 |
|
6144 | 6158 |
|
6145 | 6159 |
-- |
6160 |
-- Name: locationevent__pull_forward_from_parent; Type: TRIGGER; Schema: public; Owner: - |
|
6161 |
-- |
|
6162 |
|
|
6163 |
|
|
6164 |
|
|
6165 |
|
|
6166 |
-- |
|
6146 | 6167 |
-- Name: party_source_id_self_ref; Type: TRIGGER; Schema: public; Owner: - |
6147 | 6168 |
-- |
6148 | 6169 |
|
Also available in: Unified diff
bugfix: schemas/vegbien.sql: locationevent: added pull-forward trigger to populate location_id from the parent event. a pull-forward trigger must be used for this (not a COALESCE in analytical_stem_view) because the locationevent cannot even be found by analytical_stem_view if it does not have an associated location.