Opened 16 years ago
Last modified 9 years ago
#120 new enhancement
Treenames used as keys
Reported by: | westram | Owned by: | devel |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Library (other) | Version: | SVN |
Keywords: | Cc: |
Description (last modified by westram)
- treenames of trees stored in are used as keys, cause the current -structure is:
/tree_data/XXX/
where XXX is the name of the (e.g. tree_demo) - the structure should be changed to
/tree_data/tree /tree_data/tree/name with content XXX
cause keys are a limited ressource
- Needed changes:
- access code
- write a fix, which once changes the way trees are stored (see nt_check_database_consistency)
Same problem exists for
- configuration names (AWT_insert_config_manager)
Change History (6)
comment:1 Changed 16 years ago by westram
- as well move node entries to extra subcontainer (e.g. nodes)
comment:2 Changed 16 years ago by westram
When changing layout:
- be careful to catch all occurrances, where -name is read from using GB_read_key(treecontainer)
- before changing it, implement #143 and increment version
comment:3 Changed 15 years ago by westram
- Component changed from Library (DB) to Library (other)
- implement together with #155
comment:4 Changed 11 years ago by westram
- Description modified (diff)
- Milestone set to work2014
comment:5 Changed 10 years ago by westram
- Description modified (diff)
comment:6 Changed 9 years ago by westram
- Milestone work2014 deleted
Note: See
TracTickets for help on using
tickets.