More evidence that it's a contentious issue.
Dave Cramer
dave.cramer(at)credativ(dot)ca
http://www.credativ.ca
On Tue, Apr 24, 2012 at 2:59 AM, Bernard <bht237@gmail.com> wrote:
> Dave,
>
> I have filed issues with Hibernate and EclipseLink. No activity at
> Hibernate. EclipseLink has a workaround for this but it does not work
> with Postgresql. It is quite difficult to get them to do anything
> because they are fine with their preferred databases e.g. Oracle,
> Mysql.
>
>
> I found this interesting:
>
> "Add support for setObject(<arg>, null)"
> https://issues.apache.org/jira/browse/DERBY-1938
>
> Bernard
>
>
> On Mon, 23 Apr 2012 15:15:56 -0400, you 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.
>>
>>Bernard, if you point this out to the projects in question what do they say ?
>>
>>Dave
>