Hi,
I am looking at two distinct layers / datastores for the purpose of getting the geosearch / sitemap module working again. Both stores are Postgis running on my laptop, as far as I can tell they're defined the same way, and I have tried deleting and recreating them, just in case there's some history lingering.
One (does support offset) appears to be org.vfny.geoserver.global.GeoServerFeatureLocking the other (does *not* support offset) is org.vfny.geoserver.global.GeoServerFeatureSource. I've also checked that it's not just the querycapabilities lying.
This is deep in unfamiliar territory for me. Can anyone tell me why I end up with one or the other?
-Arne
Arne Kepp wrote:
Hi,
I am looking at two distinct layers / datastores for the purpose of getting the geosearch / sitemap module working again. Both stores are Postgis running on my laptop, as far as I can tell they're defined the same way, and I have tried deleting and recreating them, just in case there's some history lingering.
One (does support offset) appears to be org.vfny.geoserver.global.GeoServerFeatureLocking the other (does *not* support offset) is org.vfny.geoserver.global.GeoServerFeatureSource. I've also checked that it's not just the querycapabilities lying.
This is deep in unfamiliar territory for me. Can anyone tell me why I end up with one or the other?
You get only "source" for the layers that are read only, a postgis
layer usually is ro when there is no primary key defined.
Cheers
Andrea
Andrea Aime wrote:
Arne Kepp wrote:
Hi,
I am looking at two distinct layers / datastores for the purpose of getting the geosearch / sitemap module working again. Both stores are Postgis running on my laptop, as far as I can tell they're defined the same way, and I have tried deleting and recreating them, just in case there's some history lingering.
One (does support offset) appears to be org.vfny.geoserver.global.GeoServerFeatureLocking the other (does *not* support offset) is org.vfny.geoserver.global.GeoServerFeatureSource. I've also checked that it's not just the querycapabilities lying.
This is deep in unfamiliar territory for me. Can anyone tell me why I end up with one or the other?
You get only "source" for the layers that are read only, a postgis
layer usually is ro when there is no primary key defined.
Cheers
Andrea
You are right as usual, I had only added and clustered on the geometry index after reading the tab delimited file, but not explicitly created a primary index.
Thank you,
-Arne