It no longer is contentious - they fixed it in Apache Derby.
On Tue, 24 Apr 2012 05:37:37 -0400, you wrote:
>More evidence that it's a contentious issue.
>On Tue, Apr 24, 2012 at 2:59 AM, Bernard <bht237(at)gmail(dot)com> wrote:
>> 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,
>> I found this interesting:
>> "Add support for setObject(<arg>, null)"
>> On Mon, 23 Apr 2012 15:15:56 -0400, you wrote:
>>>>  (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 ?
In response to
pgsql-jdbc by date
|Next:||From: Dave Cramer||Date: 2012-04-24 17:44:56|
|Subject: Re: Cannot pass null in Parameter in Query for ISNULL|
|Previous:||From: Dave Cramer||Date: 2012-04-24 13:30:51|
|Subject: Re: Please could we have support for isValid() method in JDBC driver?|