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 [email protected]
