-
@andrzej.wojcik feel free to comment if anything is missing.
-
I do see a need for a storing value for
user_id, node, key
but I do not see a point in having anything deeper. Accessing those "deep" values is not fast and I do not see how it would be better than storing just XML or other type of a structure as a value. -
exactly. With
user_id, node, key
we have a simple table without tree like dependencies. If we would introduce alternative tonodes
table we would end up with a tree and possibility to end up withdeep
relations. That would reduce number of joins and improve performance of the database queries.
Type |
Task
|
Priority |
Normal
|
Assignee | |
Version |
Candidate for next major release
|
Spent time |
0
|
Iterations
Issue Votes (0)
Current UserRepository implementation should be improved:
tig_nodes
and add 'node' column intig_pairs
parent_node
column intig_pairs
to maintain tree-like structurelastModified
column totig_pairs
to help track changes made to entries(and maybe "value hash"? in a vain similar to current UserRepoRepository detection if value was modified)Subsequently, UserRepoRepository should be adjusted and store items individually.
Motivation: