Miles Jordan ha scritto: > Unfortunately in my experience you can only use one schema per oracle > datastore. However you should be able to use any user that has access > to the table to connect to it IF and only if you have set the schema > in the datastore configuration. > > That is really suboptimal if you are serving up layers from different > schemas, because you can't use connection pooling unless you use > JNDI. > > I think the reason you can't use one user to access multiple schemas > with one datastore is because when you choose a layer from the layer > chooser I don't think it keeps a record of which schema the layer > comes from (just guessing).
Correct. This is something that has been bugging me as well. I've opened a jira issue about this: http://jira.codehaus.org/browse/GEOT-2833 The change required is not going to be small thought, it's going to change the core classes as well as all of the dialects. Anyone interested in giving it a crack? > So I think the best thing for Geoserver is either to enforce the use > of a schema name in the Oracle datastore configuration or to only > allow selection of layers from tables that the user owns. Probably > the first solution would be best, I think. Sounds like a viable short term workaround, thought I don't like the idea very much. Care to open a request? Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
