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.
Prior versions of the JDBC specification were not clear or concise as
to what a developer and or a user could expect. This as a JDBC driver
developer while at Sybase i found extremely frustrating.
These methods have been in the JDBC spec since 1.0. We will not be
removing them from the spec
Actually the intent has always been there, just not clearly articulated.
If a driver claims to support a data type such as
Blob/Clob/Array...etc... it is expected that all methods on the
interface are fully implemented and just do not throw an exception.
It is just JDBC 4.0 that i am taking
Daniel John Debrunner wrote:
Lance J. Andersen wrote:
The compliance chapter has seen significant clarifications for JDBC 4 to
clarify what is and is not required. If you implement and interface for
a data type such as blob/clob all methods must be implemented otherwise
you do
Lance J. Andersen wrote:
Prior versions of the JDBC specification were not clear or concise as to
what a developer and or a user could expect. This as a JDBC driver
developer while at Sybase i found extremely frustrating.
These methods have been in the JDBC spec since 1.0. We will not be
DJD question According to which section of JDBC 3.0?
Then this is about JDBC 4.0 compliance and not JDBC 3.0.
yes and no, the intent has always been there just not clear in print
If you feel more comfortable stating this is JDBC4 so be it, but again
the intent has always been
[
http://issues.apache.org/jira/browse/DERBY-1283?page=comments#action_12377820 ]
Rick Hillegas commented on DERBY-1283:
--
Dan's comment kicked off a lively discussion on derby-dev, under the subject
line [jira] Commented: (DERBY-1283) Fill
Daniel John Debrunner wrote:
We will not be
removing them from the spec and just because something is deprecated, it
does not mean that it should not be implemented or ignored. It just
means that there are alternative methods that are recommended.
Wow! This is not how I understood the word
I really do not want a war of words here as it serves zero purpose.
Methods that are deprecated are never guaranteed to be removed though it
is possible they could. There are no plans to remove any methods that
are deprecated from JDBC and going forward unless there is a method that
is
Rick Hillegas wrote:
Lance J. Andersen wrote:
...
If you want to ask the question a different way and revisit whether
setUniCodeStream can be considered optional, then do so please and i
will consider it and have that discussion with the EG. JDBC drivers
that have been around since the
[
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,
[
http://issues.apache.org/jira/browse/DERBY-1283?page=comments#action_12377663 ]
Daniel John Debrunner commented on DERBY-1283:
--
Also, which section of JDBC 3.0 spec indicates that Derby is not currently in
compliance with JDBC 3.0 with
Very simple, just because it is deprecated, it does not mean it can be
ignored. Bottom line, it is required to be there.
There are no plans to remove these methods from JDBC.
Daniel John Debrunner (JIRA) wrote:
[
The compliance chapter has seen significant clarifications for JDBC 4
to clarify what is and is not required. If you implement and interface
for a data type such as blob/clob all methods must be implemented
otherwise you do not support the data type.
Daniel John Debrunner (JIRA) wrote:
Lance J. Andersen wrote:
Very simple, just because it is deprecated, it does not mean it can be
ignored. Bottom line, it is required to be there.
According to which section of JDBC 3.0?
Dan.
Lance J. Andersen wrote:
The compliance chapter has seen significant clarifications for JDBC 4 to
clarify what is and is not required. If you implement and interface for
a data type such as blob/clob all methods must be implemented otherwise
you do not support the data type.
So this is a
Lance J. Andersen wrote:
The compliance chapter has seen significant clarifications for JDBC 4 to
clarify what is and is not required. If you implement and interface for
a data type such as blob/clob all methods must be implemented otherwise
you do not support the data type.
Is this a recent
17 matches
Mail list logo
