As Andrea says this was considered and discussed. And as Andrea kindly
pointed out the WFS spec actually mandates that we don't use multiplicity
and complex feature references.
That said I don't think we should rule out using the Join construct to do
that... just that I would like it to be an implementation detail if
possible. Or maybe we add a flag some where in the api to change how results
are returned. Not sure. But I agree with Andrea that this not joining, its
mapping (although implemented via a join).
On Wed, Jun 22, 2011 at 4:24 AM, Jody Garnett <[email protected]>wrote:
> Different problem my suggestion was an alternative to having to repeat the
> row:
>
>>
>>> Park(fid:32,geom:Polygon, name:String, Lake(fid:21):SimpleFeature,
>>> POI:SimpleFeature)
>>> Park(fid:32, geom:Polygon, name:String,
>>> Lake(fid:22):SimpleFeature, POI:SimpleFeature)
>>>
>> I think Justin already clarified in another mail in this thread that this
>> won't be covered.
>>
>
> Justin clarified the feature being returned multiple times (as shown
> above). Nothing wrong with that I was asking
> if he had considered multiplicity. Sounds like he has and has left it as an
> exercise for another time if someone
> is interested.
>
> Cheers,
> Jody
>
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today.
http://p.sf.net/sfu/quest-sfdev2dev
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
