From commons-user-return-5175-apmail-jakarta-commons-user-archive=jakarta.apache.org@jakarta.apache.org Mon Oct 06 17:06:16 2003 Return-Path: Delivered-To: apmail-jakarta-commons-user-archive@www.apache.org Received: (qmail 38928 invoked from network); 6 Oct 2003 17:06:16 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 6 Oct 2003 17:06:16 -0000 Received: (qmail 3718 invoked by uid 500); 6 Oct 2003 17:06:04 -0000 Delivered-To: apmail-jakarta-commons-user-archive@jakarta.apache.org Received: (qmail 3695 invoked by uid 500); 6 Oct 2003 17:06:04 -0000 Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Users List" Reply-To: "Jakarta Commons Users List" Delivered-To: mailing list commons-user@jakarta.apache.org Received: (qmail 3682 invoked from network); 6 Oct 2003 17:06:03 -0000 Received: from unknown (HELO smtp.easystreet.com) (206.26.36.40) by daedalus.apache.org with SMTP; 6 Oct 2003 17:06:03 -0000 Received: from apache.org (dsl-208-161-106-6.dsl.easystreet.com [208.161.106.6]) by smtp.easystreet.com (Postfix) with ESMTP id 5BE0C84537D for ; Mon, 6 Oct 2003 10:06:07 -0700 (PDT) Message-ID: <3F81A0CD.8070702@apache.org> Date: Mon, 06 Oct 2003 10:05:17 -0700 From: "Craig R. McClanahan" User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jakarta Commons Users List Subject: Re: [BeanUtils] ResultSetDynaClass lowerCase option References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Gary Shea wrote: >I've run into a situation where the ResultSet DynaClass support is >broken by setting the lowerCase field true. Hsqldb sets column names to >upper case by default. If lowerCase is true, the first access to the >row goes boom. I'm wondering if this is because lowerCase is a work in >progress, or because this is expected behavior? The javadoc suggests >that lowerCase is intended to ease dealing with varying JDBC >implementations, but my impression of the current lowerCase code is that >it's very fragile and will only work if the JDBC implementation returns >the column names in lower case already! My apologies if I'm missing >something... > > Without a specific example of what "goes boom" means, it is not possible to tell whether this is a bug in BeanUtils or a user error. However, the design intent of the "lowerCase" flag is that, no matter what the database returns for column names, the *entire* property name (as seen in the DynaBeans) is in lower case. For example, if your database returned "ACCOUNT_ID" as a column name, the property in DynaBeans would be treated as "account_id" instead. If you are seeing something different, please post a bug report with a detailed example: http://nagoya.apache.org/bugzilla >I'm happy to contribute a fix, if something needs fixing, but thought >I'd better check first... > >Regards, > > Gary > > Craig --------------------------------------------------------------------- To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-user-help@jakarta.apache.org