[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [udig-users] Oracle: sdo_aggr_mbr vs user_sdo_geom_metadata
|
Hi Brandon.
We had the previous version of our oracle support use the geom
metadadata table; and I after treading the oracle manuals I though
this was the correct approach to determine bounds.
I got lots of negative feedback; apparently this table is not often
filled in with the correct information and cannot be trusted. With
that in mind, when geotools created their "jdbc-ng" rewrite for oracle
support they did not even considering taking the geom metadata table
code used previous.
If you like we can make the feature request for GeoTools and see what they say.
With respect to SELECT SDO_AGGR_MBR ... I had thought that we avoided
doing this for uDig 1.2.0 - instead assuming a default max extent
based on the coordinate reference system.
When Maurcio returns from vacation we can ask him, he performed the
oracle testing for 1.2.0.
Jody
On Thu, Aug 19, 2010 at 4:37 AM, Bergenroth, Brandon
<bbergenroth@xxxxxxx> wrote:
> I have yet to see uDig (including 1.2.0) use user_sdo_geom_metadata,
> instead, it seems to always insist on running
>
> SELECT SDO_AGGR_MBR(GEOMETRY) FROM BIG_SPATIAL_TABLE
>
> for every table in the schema.
>
> Will uDig ever use user_sdo_geom_metadata? Running a full table scan on
> every spatial table makes it pretty much useless for anything but a
> trivial amount of data.
>
> Thanks,
> Brandon
>
>
>
> _______________________________________________
> udig-users mailing list
> udig-users@xxxxxxxxxxxxxxxxxxxxx
> http://lists.refractions.net/mailman/listinfo/udig-users
>
