> This looks like an insert to a varchar field not a Date
> field. So I changed the column to a varchar and it worked.
> So .... I think this is not what I want. Also, this doesn't
> seem like the correct *default* behavior for jdbc-type of Date.
Ok, so apparently not everyone is as interested in this as I am. Anywho
-- I tracked this little bugger down:
org.apache.ojb.broker.platforms.PlatformOracleImpl.java
public void setObjectForStatement(PreparedStatement ps, int index,
Object value, int sqlType) throws SQLException
{
[snip]
else if (sqlType == Types.DATE) {
ps.setDate(index, (Date)value);
}
[snip]
}
Any reason why people wouldn't want to use a Date field in this
scenario?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
