On Fri, Mar 11, 2011 at 5:40 PM, Pedro Mendes <[email protected]> wrote: > Don´t know if Steve did overcome this issue, but the use the > function SDO_TUNE.EXTENT_OF will prevent having a feature with 2 or more > geometry columns from an Oracle datastore. This is due an apparent bug in > the function when the table as more than one geometry column. > Maybe getOptimizedBounds should use SDO_AGGR_MBR?
That's what we do if the "estimated extents" flag is not checked. It's also a lot slower, if you have millions of records that can peg a Oracle instance busy for various minutes Cheers Andrea -- ------------------------------------------------------- Ing. Andrea Aime GeoSolutions S.A.S. Tech lead Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 962313 mob: +39 333 8128928 http://www.geo-solutions.it http://geo-solutions.blogspot.com/ http://www.youtube.com/user/GeoSolutionsIT http://www.linkedin.com/in/andreaaime http://twitter.com/geowolf ------------------------------------------------------- ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
