[ http://issues.apache.org/jira/browse/IBATIS-39?page=comments#action_57333 ] David Putnam commented on IBATIS-39: ------------------------------------
Ok, I think I have resolved this through additional debugging sessions and re-reading the four documents. I changed the in-line parameter references from #property# to #property:JDBCTYPE# and the null gets put in the database without a problem. It seems that the best guess that the BasicParameterMap.setParameter can make is the Types.NULL or Types.OTHER. However if the TypeHandler were called regardless of the null-ness of the propertyValue, the specific TypeHandler (DateTypeHandler in this case) could make a better guess at an appropriate JDBC type to use if one was not specified. Maybe this issue could be changed to an Enhancement Request for that purpose. > Unable to store null attributes as null values in a column > ---------------------------------------------------------- > > Key: IBATIS-39 > URL: http://issues.apache.org/jira/browse/IBATIS-39 > Project: iBatis for Java > Type: Bug > Components: SQL Maps > Versions: 2.0.8 > Environment: Standalone (no appserver) application in Java 1.4.2 connecting > to Sybase 12.5 using Sybase JDBC2 drivers (jconn2.jar) > Reporter: David Putnam > Priority: Blocker > Attachments: Customer.ibatis.xml, Customer.java, ibatis.xml, program log.txt > > Any null attribute throws a SQL Exception with an Unsupported JDBC type 0 > message. When I get back to the office I will copy actual error message and > configuration information into here. > BTW I created this because I am not sure if there is a better forum for this. > Hopefully I am not cluttering this area with a simple configuration problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
