Merge Provenance*DB classes in a single ProvenanceDB
now most of the specific logic is handled in sql functions or
templatized sql code (e.g. relation_add()), it makes no sense to keep
two classes.
Description
Description
Details
Details
- Provenance
douardda Authored on Jul 21 2021, 11:31 AM douardda Pushed on Aug 6 2021, 10:58 AM - Differential Revision
- D6015: Use stored SQL functions for content_find_{all,one}() and merge Provenance*DB classes in a single ProvenanceDB
- Build Status
Buildable 22914 Build 35731: test-and-build Jenkins console · Jenkins