openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Johnson (JIRA)" <j...@apache.org>
Subject [jira] Created: (OPENJPA-164) Need better logging on Java field type to SQL type mapping and exceptions
Date Wed, 07 Mar 2007 05:36:24 GMT
Need better logging on Java field type to SQL type mapping and exceptions
-------------------------------------------------------------------------

                 Key: OPENJPA-164
                 URL: https://issues.apache.org/jira/browse/OPENJPA-164
             Project: OpenJPA
          Issue Type: Improvement
            Reporter: Nick Johnson


When a Java field and its corresponding SQL field are of incompatible types (as can happen
with programming errors), OpenJPA presently just wraps the exception thrown by the JDBC driver.
 For example, if the type is declared as long in Java but boolean in PostgreSQL, a PostgreSQL
error that the value "f" is not compatible with the type BigDecimal.

The problem is that there's no indication of which mapped class is responsible for the exception,
which can be a problem for a class with many relationships.  Any of the related classes could
have caused the problem.

Better logging (probably at level TRACE) around calls to resultSet.getX would greatly help
in debugging these problems.  Just knowing the classname and the field name the JDBC get is
being called for would be tremendously helpful.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message