openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Boblitz (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OPENJPA-1998) NPE getTableNameForMetadata when running SchemaTool reflect against Postgres DB
Date Fri, 13 May 2011 12:14:47 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032979#comment-13032979
] 

John Boblitz commented on OPENJPA-1998:
---------------------------------------

Further debugging and experimenting led me to the attribute "supportsNullTableForGetImportedKeys"
which is set to true in the PostgresDictionary class.  Changing this to false in DBDictionary:4325
solves the problem.



> NPE getTableNameForMetadata when running SchemaTool reflect against Postgres DB
> -------------------------------------------------------------------------------
>
>                 Key: OPENJPA-1998
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1998
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jdbc
>    Affects Versions: 2.1.0
>         Environment: Windows 7, Eclipse Helios 3.6.2, remote Postgres DB 8.4. on Debian
squeeze 
>            Reporter: John Boblitz
>         Attachments: output.txt
>
>
> When running the SchemaTool to reverse a DB Schema, an NPE occurs at getTableNameForMetadata
for foreign keys (tables and pk / uq indices works correctly!)  Debugging shows that the tableName
parameter is null when invoked.  The NPE is caused by the invocation of tableName.getUnqualifiedName()
... tableName is still null at that point!

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message