Hi Craig,
Craig L Russell wrote:
Hi Lance,
On Jul 17, 2006, at 8:55 AM, Lance J. Andersen wrote:
The JDBC methods should, as much as the possibly can, be consistent
with the behavior of methods in the JDK.
I agree with your point here. I think all of us are saying that there
is no inconsistency with zero length Strings in JDK. All of the
methods we've looked at are consistent with allowing the APIs to
handle zero length Strings as a simple boundary condition. The only
thing that's a bit hard to grok is the fact that JDBC generally uses
1-origin indexing while JDK uses 0-origin. But everything in the API
allows zero-length Strings.
This issue has nothing to do do with zero-length Strings, but the valid
parameter values for getSubString(). The javadocs currently make no
claim on *any* values, so it is open to interpretation.
As i said, it really boils down to what the EG will agree to document at
this point in time as the correct behavior and until i conclude that
discussion, there really is nothing more i can provide for input.
Regards
Lance
This specific issue could easily be argued either way and I see it
from a different point of view
I haven't seen anything in your examples (once corrected) that give
you a different point of view. Can you please re-read the thread and
tell us where there is a problem?
Craig
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!
