Skip to content

Use stored SQL functions for content_find_{all,one}() and merge Provenance*DB classes in a single ProvenanceDB

David Douard requested to merge generated-differential-D6015-source into generated-differential-D6015-target

instead of generated specific SQL queries in python. This allows to make Provenance*DB classes easily mergeable (following revision).

So 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.

Depends on !33 (closed)

Migrated from D6015 (view on Phabricator)

Merge request reports