Skip to content

Migrate to new data structure, sqlalchemy and alembic #2

@emilymclean

Description

@emilymclean

Looking towards future development, it would be far quicker and easier to develop new tools if the data structure was represented using an ORM with proper versioning and automatic upgrades. I've designed a far more flexible general content representation, which would also necessitate a restructure of how processors work (for a future task).

image

In addition to this general layout, specific processors should manage their own tables/databases, specific to their use case. Currently, this is only needed for the PhashProcessor, for which a schema has already been designed.

image

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

Status

In Progress

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions