2013/10/25 Andrea Aime <[email protected]>
> It invalidates GeoServer one. The one managed by the stores is private, no
> way to reach it and
> drop it. Different stores do it in a different way, some do not have it at
> all, but for JDBC ones
> it is crucial, because of the high cost in figuring out the feature type
> structure (many queries
> to the DBMS are normally required)
>
So when I am removing the featuretype the store caches information about
its structure just in case I would create it again in the near future, is
it right?
And is it this behaviour not ovveridable by the calling method?
Or is it more wise a conservative approach and avoiding to destroy
information that may turn useful?
Thank you very much for your time and the extremely clear explanation, as
usual.
Cheers,
Stefano
---------------------------------------------------
41.95581N 12.52854E
http://www.linkedin.com/in/stefanoiacovella
http://twitter.com/#!/Iacovellas
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
