db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dyre.Tjeldv...@Sun.COM
Subject Re: [jira] Commented: (DERBY-1283) Fill in a deprecated but mandatory JDBC3 method: PreparedStatement.setUnicodeStream()
Date Sat, 10 Jun 2006 14:20:00 GMT
"Daniel John Debrunner (JIRA)" <derby-dev@db.apache.org> writes:

>     [ http://issues.apache.org/jira/browse/DERBY-1283?page=comments#action_12377662 ]

> Daniel John Debrunner commented on DERBY-1283:
> ----------------------------------------------
> Seems strange to implement a deprecated api. Section 6.7 says
> "Deprecation refers to a class, interface, constructor, method or field that is no longer
> recommended and may cease to exist in a future version."
> Why  would Derby implement a method we don't want applications to use?

Perhaps because the same method is described in Derby's own
documentation? :)

Reference guide (Alpha manuals) -> JDBC -> PreparedStatement -> 
"PreparedStatements and streaming columns"

Did this method perhaps exist at some point, and was then later removed? 

Now that we have persuaded the EG to make the method optional, perhaps
we should get our own house in order, as it were, and update the
documentation? If nobody objects I'll create a doc jira for this.


View raw message