Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1251.1)
Subject: Re: limiting the selectors in the select list
From: Lukas Kahwe Smith <mls@pooteeweet.org>
In-Reply-To: 
 <CAB-0WTC0sNDp=KvwmcFCJA9FroFW5Nzp0y4=Bpc_Q32M7wjbEQ@mail.gmail.com>
Date: Mon, 12 Dec 2011 11:35:14 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <D868E598-CA8E-4387-9AFD-3D9BAB22D300@pooteeweet.org>
References: <C6D713C4-1652-43EB-9CE8-69EC3264B362@pooteeweet.org>
 <C1161879-D367-46C9-8D28-FE2882C74826@pooteeweet.org>
 <78A080B6-0623-4E9C-863A-FBB2244A6F61@pooteeweet.org>
 <CAB-0WTC0sNDp=KvwmcFCJA9FroFW5Nzp0y4=Bpc_Q32M7wjbEQ@mail.gmail.com>
To: users@jackrabbit.apache.org


On Dec 12, 2011, at 11:20 , Alex Parvulescu wrote:

> So, you are right you'll always get the full selector content is =
returned
> in a row (both "a" and "b" in this case), but 'getColumnNames' will =
tell
> you what was in the 'SELECT' specifically.
> I don't know if this should be considered extra weight on the remoting
> layer, and what would be the gain of filtering out unneeded selector =
info
> before pushing the info over the wire.

I figured it out since the primaryType is prefixed with the selector =
defined in the FROM

> Back to your example, I don't understand why you would want to know =
what
> was the default selector, as you are the one building the sql in the =
first
> place. So you probably know that you are looking for "data.*" .


This is for a generic layer.
For PHPCR we have an ODM, which allows you to map nodes to documents.

regards,
Lukas Kahwe Smith
mls@pooteeweet.org