From: | Dave Cramer <Dave(at)micro-automation(dot)net> |
---|---|
To: | Felipe Schnack <felipes(at)ritterdosreis(dot)br> |
Cc: | pgsql-jdbc <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: setUseServerPrepare & typecasts |
Date: | 2002-11-14 10:37:34 |
Message-ID: | 1037270254.5146.66.camel@inspiron.cramers |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Well, in postgres it certainly isn't necessary, however I would suspect
that one of the vendors that was involved in creating the spec required
it.
Dave
On Thu, 2002-11-14 at 04:59, Felipe Schnack wrote:
> I never understood why I have to specify a data type when setting a
> column to NULL in jdbc's PreparedStatement.setNull() method. Someone can
> explain to me?
>
> On Wed, 2002-11-13 at 23:57, Aaron Mulder wrote:
> > On Wed, 13 Nov 2002, Scott Lamb wrote:
> > > Ahh, but the JDBC 3.0 specification does. Section 13.2.2.3 says "if a
> > > Java null is passed to any of the setter methods that take a Java
> > > object, the parameter will be set to JDBC NULL". So it should work.
> >
> > Oops, you're right. I had it in my head that you _had_ to use
> > setNull, but I see that's not really required.
> >
> > Aaron
> >
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 3: if posting/reading through Usenet, please send an appropriate
> > subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> > message can get through to the mailing list cleanly
--
Dave Cramer <Dave(at)micro-automation(dot)net>
From | Date | Subject | |
---|---|---|---|
Next Message | Barry Lind | 2002-11-14 10:51:03 | Re: setUseServerPrepare & typecasts |
Previous Message | Felipe Schnack | 2002-11-14 09:59:43 | Re: setUseServerPrepare & typecasts |