Return-Path: Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 56848 invoked from network); 9 Mar 2000 00:20:56 -0000 Received: from phoenix.webslingerz.com (balld@206.66.49.24) by locus.apache.org with SMTP; 9 Mar 2000 00:20:56 -0000 Received: from localhost (balld@localhost) by phoenix.webslingerZ.com (8.8.7/8.8.7) with ESMTP id TAA25242 for ; Wed, 8 Mar 2000 19:19:39 -0500 Date: Wed, 8 Mar 2000 19:19:39 -0500 (EST) From: Donald Ball To: cocoon-dev@xml.apache.org Subject: Re: Problems with Cocoon 1.7 sql processing In-Reply-To: <38C423F7.7D6BB3F6@include-datorkonsulter.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N On Mon, 6 Mar 2000, Anders Heintz wrote: > Hello again... > > > When I am trying to extract data from the database, > > VARCHAR and INT fields are correct, but TEXT and BLOB > > fields are not. Seems like the values returned are > > references, they are definitely not strings. > > Solved this by changing from a ResultSet.getObject() call > to a ResultSet.getString() in SQLProcessor.processQuery. > I would appreciate comments, will anything malfunction due > to this change? It will certainly break things on some other databases. Jeez, JDBC sucks in terms of cross-driver compatibility. I think the proper thing to do in this instance would be to check to see if the Object is a 'reference' (I think you mean a Reader or InputStream?) and if so, to serialize that to a String. That should ensure maximum cross-driver compatibility. Do you think that'd work? If so, can I beg for a patch? - donald