Skip to content

support non-ERAV data models #3

Description

@sheppard

The current implementation relies heavily on vera. Generalize this to support three use cases:

  • Populating a single table
  • Populating an EAV structure (e.g. wq.db.patterns.annotate or any EAV implementation)
  • Populating an ERAV structure (i.e. vera)

Obviously, only the ERAV structure will be able to ensure data can be imported without clobbering existing data in the database.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions