Mailing-List: contact jena-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jena-dev@incubator.apache.org
Message-ID: <26443366.74571293744465248.JavaMail.jira@thor>
Date: Thu, 30 Dec 2010 16:27:45 -0500 (EST)
From: "Damian Steer (JIRA)" <jira@apache.org>
To: jena-dev@incubator.apache.org
Subject: [jira] Updated: (JENA-22) OpAsQuery doesn't support OpGroup
In-Reply-To: <32787086.74491293743985242.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/JENA-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Damian Steer updated JENA-22:
-----------------------------

    Attachment: OpAsQuery_group.patch

This patch implements support for OpGroup in OpAsQuery. It's a little convoluted for two reasons:

 1. Projecting expressions has to be handled right at the end. Project is typical visited before grouping, and setting project twice for a variable causes an error.
 2. Simple counts involve an internal variable assignment. I've tried to catch this, but it's not elegant or general.

Tests are included.

> OpAsQuery doesn't support OpGroup
> ---------------------------------
>
>                 Key: JENA-22
>                 URL: https://issues.apache.org/jira/browse/JENA-22
>             Project: Jena
>          Issue Type: Bug
>          Components: ARQ
>            Reporter: Damian Steer
>         Attachments: OpAsQuery_group.patch
>
>
> OpAsQuery can't create some fairly straightforward queries, for example select (count(*) as ?cs) { ?s ?p ?o }.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.