Actions
Task #562
openflatten the mappings
Start date:
02/14/2013
Due date:
% Done:
0%
Estimated time:
Activity type:
Description
- put the destination table at the beginning of the mapping, rather than nesting it within a hierarchy of tables it has fkeys to
- requires #561 to be done because autogenerated pkeys require the nested normalization format to be propagated properly
- note that normalized VegCore's
traceable.id_by_source
now provides an alternate pkey that can be used for duplicate-merging when the referenced table provides enough for a natural key (causing a natural key to be used fortraceable.id
), but the referencing table uses a source-specific numeric key (which is enough for a collision ontraceable.id_by_source
but nottraceable.id
)
Updated by Aaron Marcuse-Kubitza over 11 years ago
- Status changed from New to Rejected
autopopulated natural pkeys actually do require the nested mappings, but these can be part of the schema instead
Updated by Aaron Marcuse-Kubitza almost 11 years ago
- Status changed from Rejected to New
normalized VegCore's traceable.id_by_source
now provides an alternate pkey that can be used for duplicate-merging, so that the flattening can still work
Actions