Craig L Russell wrote:
You can always work around odd code on the other side of an
incompletely defined interface. But you probably have code on the
Derby side that also checks for the clob.length() == 0 and take some
extraordinary action.
So much easier for neither side to check for zero length and let the
natural boundary condition happen.
I am happy that you agree that the original DDLUtils code was perfectly
reasonable at not as Lance described it. I will exit this issue now
and allow you, Lance, or someone else with interest determine the
correct behavior, check it with Derby and file a Derby bug if needed.
Kathey
- Re: should Clob.getSubstring() allow length of 0? Kathey Marsden
-