On Thu, Apr 4, 2013 at 4:57 PM, Gabriel Roldan <[email protected]> wrote:
> Hey, just a question.
>
> What would be the impact to geoserver if a datastore does not respect the
> convention of providing feature ids as <simple type name>.<backend
> identifier>
>
The issue would just be that featureid in WFS GET has a lower chance to
work, since it becomes higher the probability to have a conflict, same id,
different store.
That said, even with the current setup it's not really impossible to have a
conflict, if you have two stores in different workspaces producing the same
ids.
> The feature id issue bothers me since a while now and would like to gather
> opinions on whether it shouldn't be mandatory for geotools datastores to
> prefix the feature ids that way. It looks to me like a WFS think leaking
> down to the data access layer, in order for GeoServer to be able of
> supplying unique ids at the service instance level, which in an ideal world
> should be GeoServer's responsibility (like in GeoServer being in charge of
> prefixing the workspace + type name to the geotools provided feature id).
>
In a perfect world, yes, the GeoServerFeatureSource/Store should wrap the
feature ids generated by the source so that we generate something like
<ws>.<publishedName>.<nativeId>, and rewrite the incoming filters
accordingly
Cheers
Andrea
--
==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more
information.
==
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------
------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire
the most talented Cisco Certified professionals. Visit the
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
