FW: [wfs-dev] sequence of Query elements

[Panagiotis (Peter) A. Vretanos]

Martin,

Oops ... I did not see this ...

The answer is that unless a SortBy is specified, there is no order
implied in the response.

However, I hope people understand that if you specify something like:

<GetFeature>
   <Query typeName="A B"/>
</GetFeature>

you do not get all the features in A and then all the features in B but
you get the cross-product of AxB.  This is what happens when you specify
a unconstrained JOIN operation.

If you want to fetch A and then B, the correct request would be:

<GetFeature>
   <Query typeName="A"/>
   <Query typeName="B"/>
</GetFeature>

In this case, you will get all the features in A and then all the
features in B.

Ciao.

Martin Kyle wrote:
> Hi Peter:
> 
> Did this get answered at all?
> 
> Martin
> 
> -----Original Message-----
> From: wfs-dev-bounces+mkyle=galdosinc.com at opengeospatial.org
> [mailto:wfs-dev-bounces+mkyle=galdosinc.com at opengeospatial.org] On Behalf Of
> Bart van den Eijnden
> Sent: April 29, 2005 5:25 PM
> To: wfs-dev at opengis.org
> Subject: [wfs-dev] sequence of Query elements
> 
> Hi list,
> 
> I could not find this explicitly in the spec, is a server supposed to  
> return the results in the same sequence as a client requests the Query  
> typenames?
> 
> If I ask for typename A first and then B in a GetFeature request, is a  
> service supposed to return the results in sequence A, B? Or can it return  
> the response in any sequence?
> 
> Best regards,
> Bart
> 

-- 
Panagiotis (Peter) A. Vretanos          CubeWerx Inc.
Big Kahuna (Senior Database Developer)  http://www.cubewerx.com
Tel. 416-701-1985 Fax. 416-701-9870     pvretano at cubewerx.com

"Black holes are where God divides by zero!" Steven Wright