Hi Jeff,
I can't see how this is limited to SPIN - the same should happen with
any other function. Could you try to put something else into the LET
clause? The ARQ engine should simply never call the LET after the
FILTER (or at least not return the result as a valid binding).
Holger
On May 27, 2009, at 10:23 AM, Schmitz, Jeffrey A wrote:
>
> Hello,
> I'm having trouble when using SPIN function arguments within a
> FILTER
> statement. E.g. using the spinsquare model I initially added a simple
> twoDimArea function that seems to work correctly:
>
> SELECT ?result
> WHERE {
> LET (?result := (?arg1 * ?arg2)) .
> }
>
> When I call it with something like:
>
> SELECT ?value
> WHERE {
> ?rec spinsquare:width ?width .
> ?rec spinsquare:height ?height .
> LET (?value := SpinLib:twoDimArea(?width, ?height))
> }
>
> the correct values are returned based on what's in the model.
> However,
> if I change the function query to filter out everything except
> squares:
>
> SELECT ?result
> WHERE {
> FILTER (?arg1 = ?arg2) .
> LET (?result := (?arg1 * ?arg2)) .
> }
>
> The filtering doesn't happen, I still get all the results. I've tried
> other variations of FILTER statements that uses only one argument and
> none of them seem to do any filtering. Should FILTER statements
> within
> SPIN Functions work?
>
> Thanks,
> Jeff
>
> >
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TopBraid Composer Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/topbraid-composer-users?hl=en
-~----------~----~----~----~------~----~------~--~---
