Hi Marwa,
The reason you see so many tables is that ever user in Oracle is
automatically granted whatever has been granted to the special PUBLIC role.
And by default, the PUBLIC role is granted access to a lot of things (to
allow users to interact with the installed packages). Most serious Oracle
DBAs spend some time locking down PUBLIC on production databases. In my
nearly empty Oracle database, PUBLIC has been granted SELECT on 2031 tables.
You cannot revoke PUBLIC since it is not a normal role.
Given this, it is better that GeoServer filters out these system tables,
since it is likely that GeoServer users would not want to publish them. I
have submitted some example code to Andrea to do this.
Regards, Paul
From: marwa El-said [mailto:[email protected]]
Sent: Tuesday, 12 October 2010 7:09 PM
To: [email protected]; [email protected]
Subject: RE: [Geoserver-users] many tables isted while creating oracle data
store
yea, i think so
because all those tables i really don't care about them and may affect on
the performance of retrieving tables because of the huge number of tables
that will be retreived from oracle data store with each user
I wanna a way to eleminate this because i'm searching my tables between
hundreds of tables to bublish my layers
if there are any permissions i can give to my user, please tell me about.
I tried Create session, select any table, connect, Resource and no way to
stop that
waiting for your reply
and thanks for help
Regards,
Marwa Elsaid
_____
From: [email protected]
To: [email protected]
Date: Tue, 12 Oct 2010 11:24:17 +1100
CC: [email protected]
Subject: Re: [Geoserver-users] many tables isted while creating oracle data
store
> Nothing funny with that. People want to publish also geometryless tables
with WFS
> occasionally, so we list everything we find.
It's usual with Oracle to filter out all the system tables, since by default
a user can see a lot of them, but they are rarely useful to an application
end user. If you make an Oracle connection with ESRI, Intergraph, etc, they
filter out tables owned by SYS, SYSTEM, MDSYS, XDB, etc, plus tables with
names containing $, tables ending in _SDOGEOM, etc, etc.
What do you think, should GeoServer also filter out the system tables? An
option on the data store?
----------------------------------------------------------------------------
-- Beautiful is writing same markup. Internet Explorer 9 supports standards
for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time
writing and rewriting code and more time creating great experiences on the
web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb
_______________________________________________ Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
