openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vitaly Lavrusevich (JIRA)" <>
Subject [jira] [Commented] (OPENJPA-2315) SchemaTool: Indexes are not getting exported
Date Mon, 31 Dec 2012 13:30:12 GMT


Vitaly Lavrusevich commented on OPENJPA-2315:

The change below resolves an issue. I cannot submit the changes due to technical issue.

File:                       org.apache.openjpa.jdbc.sql.OracleDictionary

Method:              public PrimaryKey[] getPrimaryKeys(DatabaseMetaData meta, DBIdentifier
catalog, DBIdentifier schemaName, DBIdentifier tableName, Connection conn) throws SQLException

Description: The change allows the generation of index’es when table name was explicitly
specified as part of input CLI arguments. It include the call to the pre-existing method getTableNameForMetadata(…)
that is already used in the several places for other operations, but here it was missed.

. . .

PreparedStatement stmnt = conn.prepareStatement(buf.toString());
        ResultSet rs = null;
        try {
            int idx = 1;
            if (!DBIdentifier.isNull(schemaName)) {
                setString(stmnt, idx++, convertSchemaCase(schemaName), null);
            if (!DBIdentifier.isNull(tableName)) {
                                                                setString(stmnt, idx++, getTableNameForMetadata(tableName),

> SchemaTool: Indexes are not getting exported
> --------------------------------------------
>                 Key: OPENJPA-2315
>                 URL:
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: tooling
>    Affects Versions: 2.2.1
>         Environment: Windows 7
> DB: Oracle 11.2
>            Reporter: Vitaly Lavrusevich
>              Labels: patch
> SchemaTool doesn't generate index information for table when the later is explicetly
specified in command line parameters.
> The issue is related to recently opened issue OPENJPA-2314

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:

View raw message