Comment 19 for bug 1058398

I think we should make it consistent with the functx function which
uses general comparison and, hence, raises an error.

We can add more functions if needed.

Matthias

On Sep 26, 2013, at 7:20 AM, Paul J. Lucas <email address hidden> wrote:

> On Sep 26, 2013, at 2:14 AM, Ghislain Fourny
> <email address hidden> wrote:
>
>> It is my recollection of the discussion we had that we wanted to not
>> throw errors in case of type mismatch, but just consider incompatible
>> values different. I am fine either way and being consistent with general
>> comparison makes sense, too.
>
> Somebody needs to make a decision.
>
> - Paul
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1058398
>
> Title:
> set-based sequence operations
>
> Status in Zorba - NoSQL Query Processor:
> In Progress
>
> Bug description:
> Implement the following set-based sequence function in a new sequence
> module:
>
> module namespace seq = "http://zorba.io/modules/sequence";
>
> declare function seq:set-intersect($seq1 as xs:anyAtomicType*, $seq2 as xs:anyAtomicType*) as xs:anyAtomicType*
> external;
>
> declare function seq:set-union($seq1 as xs:anyAtomicType*, $seq2 as
> xs:anyAtomicType*) as xs:anyAtomicType* external;
>
> declare function seq:set-except($seq1 as xs:anyAtomicType*, $seq2 as
> xs:anyAtomicType*) as xs:anyAtomicType* external;
>
> - The function should use value comparison but use false instead of an error in case of a type mismatch.
> - JSONiq module
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/zorba/+bug/1058398/+subscriptions