Opened 10 years ago

Last modified 2 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 DB are used as keys, cause the current DB-structure is:
    /tree_data/XXX/
    
    where XXX is the name of the tree (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:
    • tree access code
    • write a DB 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 10 years ago by westram

  • as well move node entries to extra subcontainer (e.g. nodes)

comment:2 Changed 9 years ago by westram

When changing tree layout:

  • be careful to catch all occurrances, where tree-name is read from DB using GB_read_key(treecontainer)
  • before changing it, implement #143 and increment version

comment:3 Changed 9 years ago by westram

  • Component changed from Library (DB) to Library (other)
  • implement together with #155

comment:4 Changed 4 years ago by westram

  • Description modified (diff)
  • Milestone set to work2014

comment:5 Changed 3 years ago by westram

  • Description modified (diff)

comment:6 Changed 2 years ago by westram

  • Milestone work2014 deleted
Note: See TracTickets for help on using tickets.