On Mon, Apr 23, 2012 at 12:15 PM, Dave Cramer <pg@fastcrypt.com> wrote:
>> [1] (from PreparedStatement.setObject): "Note: Not all databases allow
>> for a non-typed Null to be sent to the backend. For maximum
>> portability, the setNull or the setObject(int parameterIndex, Object
>> x, int sqlType) method should be used instead of setObject(int
>> parameterIndex, Object x). "
>> ---
>
>
> This was essentially Oliver's argument. The spec specifically tells
> you what to do.
Spec or no, if everyone else supports this, it'd be useful to offer
compatibility here (contingent, of course, on level of effort and
hackiness required)...
> Bernard, if you point this out to the projects in question what do they say ?
That's a good question: it's probably easier to address the issue in
the ORM than in the driver (the ORM should have enough information to
call the proper setNull).
---
Maciek Sakrejda | System Architect | Truviso
1065 E. Hillsdale Blvd., Suite 215
Foster City, CA 94404
(650) 242-3500 Main
www.truviso.com