cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 23542] - [PATCH] Fix Bug: Better handling of CLOB in esql (get-xml) and handling of Oracle 'temporary lobs'
Date Wed, 09 Mar 2005 21:01:58 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=23542>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=23542





------- Additional Comments From hip@cs.okstate.edu  2005-03-09 22:01 -------
Please, please, please check for null on any method in ResultSet,
CallableStatement, etc. that can return a object.  Currently in cocoon-2.1 (as
of today) everywhere ResultSet.getBlob(), ResultSet.getClob(), even some
Result.getString() do not have a no null check before the return object is used.
This causes a NPE when the database contains a SQL NULL for the desired field.

Hopefully I'll have a patch in a few days.

Also the methods in EsqlHelper.getStringOr..., do they always return a String or
can they return null?

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Mime
View raw message