[Helma-user] managing helma collections

[tobias.schaefer at orf.at]

hi joshua

thanks for this detailed plan; i am amazed that you worked out all this in your head only...
:)

> getOrderedView returns a collection which has these properties (in
> the logical sense): 1) contains the same set of objects as the
> _children of the collection (typically a HopObject) that called
> it--no more nor less 2) its children may be in a different order from
> that in which they are mapped in the creator object 3) has [almost]
> all the usual methods of HopObject 4) but you can't extend it, b/c
> it's actually a Bean (or something) and created in Java code, not
> JavaScript code 5) stays in sync with its creator collection in that
> it sees deletes and adds in real time   

with getOrderedView do you refer to the already built-in helma method or is this also the name of your theoretical implementation?

helma's getOrderedView currently has some limitations which make it impossible to use ordering on tables defined via additionalTables in a type mapping [1].

> It would be pretty easy to get 1, 2 and 3, improve on 4, and lose 5.
> 4 is nice in principle, but not all that important for what appears
> to be the most common use case (get a subset of a sorted list of the
> children so we can easily display them). 

i am not so sure about this. it's a great strength of helma to update cached collections accordingly. whenever i ran into a sync problem here it got really confusing.

ciao,
tobi

--
[1] http://helma.org/bugs/show_bug.cgi?id=532