Re: JDBC problem with dates and ANYELEMENT type

>> Any suggestions how to work around this so we can still use ANYELEMENT
>> and pass in DATE?

> You can put a cast into the query itself "SELECT ?::date".

Nah... that's no good. The same query string is used for many different types in my app - such approach would require
meto parse the SQL string and append cast to date when argument is java.sql.Date.  I'll leave this as last-ditch
approach.

What are the potential implications if I patch setDate() method in AbstractJdbc2Statement to pass OID.Date instead of
'unspecified'?Would that break anything else? We don’t use timestamps anywhere in the app yet, so I'm not really
worriedabout timezone being potentially screwed up. 

Peter