[
https://issues.apache.org/jira/browse/OPENJPA-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13541367#comment-13541367
]
Vitaly Lavrusevich commented on OPENJPA-2314:
---------------------------------------------
The changes that resolve the issues are listed below. I cannot supply a patch
due to technical issues.
File: org.apache.openjpa.jdbc.schema.SchemaGenerator
Method: private static Object[][] parseSchemasList(DBIdentifier[]
args)
Change: adding || path.getType() == DBIdentifierType.SCHEMA)
. . .
// if just a schema name, map schema to null
if ((DBIdentifier.isNull(table)
|| path.getType() == DBIdentifierType.SCHEMA) && !schemas.containsKey(schema)) {
schemas.put(schema, null);
} else if
(!DBIdentifier.isNull(table)) {
> SchemaTool : Cannot export definition of specific schema from Oracle DB
> -----------------------------------------------------------------------
>
> Key: OPENJPA-2314
> URL: https://issues.apache.org/jira/browse/OPENJPA-2314
> Project: OpenJPA
> Issue Type: Bug
> Components: tooling
> Affects Versions: 2.2.1
> Environment: Windows 7
> DB: Oracle 11.2
> Reporter: Vitaly Lavrusevich
> Labels: patch
>
> Schema Tool outputs an empty list of tables when concrete schema is specified
> in command line parameters.
--
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
