> I would have no problem to get as result a "list of tuples", where
> every tuple value has a different type, e.g.
>
> 1. Match: [ 23, "Rumsti", <some topic node> ]
> 2. Match: [ 42, "Ramsti", <some other node> ]
> .. ^^ ^^ ^^
> || || ||
> number|| ||
> || ||
> string map-fragment
>
> We have this in SQL, XQuery, so why not in TMQL?
What bothers me is the mix between scalar types and non scalar types
(topic node in this case).
> > 3. Should the scopes, and the variants of the base name be retrieved
> > with the base names, so actually a structure is retrieved, or
> > should the base names retrieved by themselves?
>
> I would say the user specifies what he wants and _exactly_ this should
> be returned. No hidden magic, no tricks and hidden intelligence.
>
I support this. I would think that one query could be:
select $topic.bn as string ....
which returns a list of baseNameString for each topic $topic (in
whatever scopes), and:
select $topic.bn as node
which returns the baseName node (including all the nodes inside it) of
the topic $topic.
I see (now) the need for both selects.
Rani
--
Rani Pinchuk
Software Engineer
Space Applications Services
Leuvensesteenweg, 325
B-1932 Zaventem
Belgium
Tel.: + 32 2 721 54 84
Fax.: + 32 2 721 54 44
http://www.spaceapplications.com
|
| 
