Implement DB callbacks bound to hierarchy

[westram]

To be able to implement #418 w/o binding callbacks to ANY of the involved sequences (which normally means "to allmost all species in ") , ARBDB shall provide a generic mechnism to bind callbacks to some "position" in the -hierarchy.

In the case needed, the position might be sth like

/species_data/species/ali_dna/data

Has to create minimal possible overhead (e.g. by first testing for matching GBQUARK).

[westram]

by log:branches/alilink@11490:11575

[epruesse]

How does the "API" look like? Do change events now simply propagate upwards in the database hierarchy? (maybe until caught?)

[westram]

Replying to epruesse:

How does the "API" look like? Do change events now simply propagate upwards in the database hierarchy? (maybe until caught?)

No - it simply allows to bind one hierarchy callback e.g. to

/species_data/species/full_name

Whenever any full_name changes, the callback will trigger, even if the -entry did not even exist when the callback has been bound.

It just avoids binding callbacks to all existing entries (and maintain that state for any newly created entries), in case you need a callback for all of them.

[westram]

forgot method to remove these callbacks. blocks #418

[westram]

forgot method to remove these callbacks. blocks #418

by log:branches/alilink@12854,12856:12861,12863,12865:12868

[westram]

mark changes that got fixed after arb 6.0.x

[westram]

Milestone renamed