[Gvsig_english] Re: Gvsig_internacional Digest, Vol 23, Issue 16

Andrea Peri andrea.peri at regione.toscana.it
Sat Dec 22 23:22:49 CET 2007


Ok,
I understand what you say.

Some suggestions:

using the ALL to find the tables with sdo_geometry you don't know if a table is readable from the account used.
An account can read (select) other tables only if it has a specific grant.


Another think is that you lost the views .
Infact a view that get from two or more tables with sdo_geometry is not reported on all_sdo_geom_metadata.
So I think you must add this control:

select owner, view_name, text from all_views where owner='<owner-name>' order by view_name;

Understand if a view has a table with sdo_geometry is a bit more complex. The text field is the definition of the view, from it you can get table_name and 
column_name and check the column_type with this sql:

select all_tab_columns.column_name, all_tab_columns.data_type, etc... from all_tab_columns where all_tab_columns.owner='<owner-name>' and ( 
(all_tab_columns.data_type='SDO_GEOMETRY') OR (all_tab_columns.data_type='SDO_TOPO_GEOMETRY') );

Just to complete:
There are even the synonym .
they are queryable with the "all_synonym" view.

Regards,
Andrea.


>Hi, Andrea,
 >
>I mean that we can read the view ALL... to find out which tables are available, not only from the user's schema, so the user will be able to add to his view 
>tables from other schemas, and we will write to USER... when the user stores a vector layer as an Oracle table.
> 
>When you use the "GeoDB" wizard to add a layer, the list of available tables you see is the content of ALL... (I understand that you can see that list.)
> 
>Regards,





More information about the Gvsig_internacional mailing list