Hi. In fact it's going to be configuration, yes. We don't need to resolve the schema at runtime. Now I was looking at the Jira, but it seems that is going nowhere. So I think I have two options now.
- to use the schemaObjectPrefix to add the schema, removing the escape of the chars and changing the DDL to not include it when creating indexes - to use the patch on the Jira (or a similar one) So my first option is easy enough for me, however it poses some questions. I'm going to make http://www.nabble.com/Use-of-diferent-or-same-schemaObjectPrefixes-td17079492.html another post about it. What do you think will be the better option? Cheers. Thomas Müller-2 wrote: > > Hi, > >> I tested and it seems it doesn't work. > > I think user name and schema name should be part of the configuration, > and shouldn't be a function. Could you explain why it can only be > resolved at runtime in your case? > > Regards, > Thomas > > -- View this message in context: http://www.nabble.com/Using-diferent-database-schemas-tp16993168p17079528.html Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
