Return-Path: Delivered-To: apmail-jakarta-commons-user-archive@www.apache.org Received: (qmail 32988 invoked from network); 6 Oct 2003 16:51:59 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 6 Oct 2003 16:51:59 -0000 Received: (qmail 80858 invoked by uid 500); 6 Oct 2003 16:51:48 -0000 Delivered-To: apmail-jakarta-commons-user-archive@jakarta.apache.org Received: (qmail 80665 invoked by uid 500); 6 Oct 2003 16:51:47 -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 80652 invoked from network); 6 Oct 2003 16:51:47 -0000 Received: from unknown (HELO ns.local.net) (12.254.168.244) by daedalus.apache.org with SMTP; 6 Oct 2003 16:51:47 -0000 Received: by ns.local.net (Postfix, from userid 501) id D077C6590B; Mon, 6 Oct 2003 12:51:50 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by ns.local.net (Postfix) with ESMTP id B63996D62F for ; Mon, 6 Oct 2003 10:51:50 -0600 (MDT) Date: Mon, 6 Oct 2003 10:51:50 -0600 (MDT) From: Gary Shea X-X-Sender: shea@ns.local.net To: commons-user@jakarta.apache.org Subject: [BeanUtils] ResultSetDynaClass lowerCase option Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 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... I'm happy to contribute a fix, if something needs fixing, but thought I'd better check first... Regards, Gary --------------------------------------------------------------------- To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-user-help@jakarta.apache.org