🚀 go-pugleaf

"Alexey Kuznetsov" <getweb@pochta.org> wrote in message news:<9j35gr$8rj$1@news.sovam.com>...
> Hello, All !
> 
> Suggest please why the following code throws an exception:
>  ...
>   Connection con = DriverManager.getConnection("jdbc:odbc:DB;uid=sa;");
>   PreparedStatement ps = con.prepareStatement("INSERT INTO log VALUES (?,
> 1)");
>   ps.setDate(1, new java.sql.Date(System.currentTimeMillis()));
>   ps.executeUpdate();
> ....
> 
> Exception in thread "main" java.sql.SQLException: [Microsoft][ODBC SQL
> Server Dr
> iver]Optional feature not implemented
>         at sun.jdbc.odbc.JdbcOdbc.createSQLException(JdbcOdbc.java:6031)
>         at sun.jdbc.odbc.JdbcOdbc.standardError(JdbcOdbc.java:6188)
>         at sun.jdbc.odbc.JdbcOdbc.SQLBindInParameterDate(JdbcOdbc.java:752)
>         at
> sun.jdbc.odbc.JdbcOdbcPreparedStatement.setDate(JdbcOdbcPreparedState
> ment.java:833)
> 
> Here is the table definition SQL statement:
> create table log (
>    execdate datetime not null,
>    toolid int not null
> )

What happens if you use java.sql.Timestamp instead of java.sql.Date? I
would suspect that Timestamp maps to "datetime" better than Date. Just
a guess... I've never used the JDBC/ODBC bridge.