From: | Bernard <bht237(at)gmail(dot)com> |
---|---|
To: | Dave Cramer <pg(at)fastcrypt(dot)com> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Cannot pass null in Parameter in Query for ISNULL |
Date: | 2012-04-24 06:59:37 |
Message-ID: | 41jcp7tqppi1r8lasf3epfntkdi8gi8rft@4ax.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2012-04-24 09:37:37 | Re: Cannot pass null in Parameter in Query for ISNULL |
Previous Message | Maciek Sakrejda | 2012-04-23 19:23:47 | Re: Cannot pass null in Parameter in Query for ISNULL |