Skip to content

Mutliple Attribute implementation #58

@chedoom3

Description

@chedoom3

Investigate the best way to implement the multiple attribute tables
We will need attributes on edges as well as nodes
(i.e. Connections and Components both need to support attributes)
If we implement key/foreign key then we will need 2 tables
Would it be better to not use the foreign key and do relational mapping ourselves (hibernate may help this)
Or is it better to use the 2 tables?

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions