Title: Message Title
|
|
|
|
Then the system administrator should configure the connection parameters properly. DSpace should not be doing this. Having DSpace guess what is the proper schema makes it impossible for the sysadmin. to specify what *is* the proper schema. And in fact we provide the configuration property "db.schema" for explicit configuration.
In any case this should not be happening in the application every time a given pooled connection is used; it should be done once per connection by the connection pool, when a connection is established.
|
|
|
|
|
|
|
I see this in initialize():
if (isOracle)
{
if (StringUtils.isEmpty(ConfigurationManager.getProperty("db.postgres.schema")))
{
sqlOnBorrow = "SET SEARCH_PATH TO " + ConfigurationManager.getProperty("db.postgres.schema").trim();
}
}
Two things seem odd:
o It's doubtful that this would ever do ...
|
|
|
|
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
