Problems with Path Expressions

, ,
1

In an earlier reply to “Problems with Collections (” "), you noted

“btw: the released version of quip is not very
stable in the path expressions passed on to
Tamino. You might encounter some problems in
more complicated paths following the collection
call. These will hopefully be fixed with the
next release.”

I am just starting to explore Quip 2.1.1.1, starting with simple queries and working up. For this purpose, I often use the Tamino demonstration base, “patient”, which features simple medical records for two medical patients, Fred Bloggs and Paul Atkins. Also named within the structure of these records are Bloggs’ doctor (A. Shamir), Atkins’ wife (Dorothy Atkins), and Atkins doctor (John Godeep).

I find that the queries

1)

{
for $x in collection(“BloggsDemo”)//patient
return
$x
}

2)

{
for $x in collection(“BloggsDemo”)/patient
return
$x
}

3)

{
let $x := collection(“BloggsDemo”)//patient
return
$x
}

and 4)

{
let $x := collection(“BloggsDemo”)/patient
return
$x
}

all produce the expected result, namely a listing of Bloggs’ complete record followed by Atkins’ complete record.

However, replacing “/patient” or “//patient” with “//surname”, produces only the result:


Bloggs
Shamir>


and does not retrieve anything from Atkins’ record.

I believe, as confirmed with Tamino’s Interactive Interface, the response should be something like the following:


Bloggs
Shamir
Atkins
Atkins
Godeep
Godeep



Is this an example of the instability in path expressions which you mentioned above? When is a corrected version likely to be available?

Thanks.

Bill

2

This is kind of strange. The problems you might
encounter in path expressions passed on to Tamino
should only occur in Path expressions far more
complex, with qualifiers and function and operator
calls.

On first glance I do not see what might be the
problem with your example. I propose to turn on
logging in the options dialog. Run your query and
have a look at the log file produce. (menu: view)

There you will see the expression actually passed
on to Tamino and the result returned by Tamino.
I guess that information will enlighten us, on
what is going on in this case.

Sven Eric

3

I just checked my CVS repository and found out
that indeed a path beginning with a double slash
is not passed on correctly to Tamino in quip
version 2.1.1. The bug was found and corrected
shortly after the release.
A corrected new official version of quip is
planned for mid may. If you cannot wait that long,
I can mail you a preview version.

Sven Eric

4

Thanks for checking. I would very much appreciate the current Preview Version of Quip.

stellhw@ccf.org