[
https://issues.jboss.org/browse/ISPN-3006?page=com.atlassian.jira.plugin....
]
Thomas Fromm commented on ISPN-3006:
------------------------------------
Yes, add schema configuration would be a feature. By default schema of the current user is
used, otherwise the configured schema.
At the moment the schema (at least for the sql statements) can be configured indirectly by
adding the schema to the table name prefix. e.g. "KOSCH.ISPN_" This worked afaik
until the table exists check was migrated to use of the Metadata.
I'd say lets fix the problem for now and create new Jira for the direct schema
support.
Oracle: TableManipulation.tableExists fails, when user has extended
permissions
--------------------------------------------------------------------------------
Key: ISPN-3006
URL:
https://issues.jboss.org/browse/ISPN-3006
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 5.3.0.Alpha1
Reporter: Thomas Fromm
Assignee: Mircea Markus
Priority: Minor
When an Oracle user has e.g. permissions to visit other schemas, the metaData.getTables
returns not only the table matadata of the schema of the current user. So if a table
exists in another user it returns true.
Solution: Since we anyway do not support explicit definition of schema name in
configuration, we can use in case of oracle the current user name as schema pattern for
getTables(..)
Other databases has different structures, e.g. in mysql the schema param seems to be
ignored. To avoid problems the chance should be limited to oracle at the moment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira