Very Computer

> I'm using PostgreSQL JDBC driver and annoyed as I cannot pass a null
> value to PreparedStatement.setBigDecimal.  If I pass a null value to the
> method, I always get an exception.

> According to the JDBC spec, I think the method must accept a null value
> and pass a SQL NULL to the database, but I may be wrong.  So is it a bug
> in the JDBC driver, or my misunderstanding of the spec?

> Thank you.  So I must always write as this?

> BigDecimal value;
> //...
> if (value == null)
>    statement.setNull(1, Types.DECIMAL);
> else
>    statement.setBigDecimal(1, value);

> > To set a database null with PreparedStatement use setNull(). Passing a Java null is the
> > wrong thing to do.

> If I must use setNull to set a JDBC NULL, this sentence is meaningless,
> isn't it?  Could you clarify the meaning of it?

>> Yes, that seems like reasonable code.

> Also, "Getting Started with the JDBC API"
> <http://www.veryComputer.com/;
> says in 6.1.5, "A JDBC NULL will also be sent to the database when a
> Java null value is passed to a setXXX method (if it takes Java objects
> as arguments)."

> Does it contradict what you say?

> > Then, what is "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."
> > (13.2.2.3 in JDBC 3.0 spec) saying?

> "For maximum portability, use setNull() to set a database null."