I added mapColumnsToProperties to the ColumnProcessor interface. Take a
look at the BasicRowProcessor.defaultProcessor implementation. Is there
any value to having this implementation or should we just use
BasicColumnProcessor? It seems like anyone using Oracle and number fields
needs BasicColum
One other note. I will be perfectly happy if we just make the
mapColumnsToProperties() method protected. But I think it would be even
better if we made it a public method in the ColumnProcessor interface.
That way, the ColumnProcessor would completely encapsulate the mapping of
both names and data
- Original Message -
From: "David Graham" <[EMAIL PROTECTED]>
To: "Jakarta Commons Developers List" <[EMAIL PROTECTED]>
Sent: Tuesday, December 02, 2003 5:46 AM
Subject: Re: [DbUtils]Making the BeanHandler... Even Smarter
>
> --- Corby Page <
--- Corby Page <[EMAIL PROTECTED]> wrote:
> Hmmm... I'm curious what the use case contexts are that people are using
> DbUtils in. I'll give you mine:
>
> I am working in an enterprise development environment where application
> developers are far removed from the DBA's that maintain the legacy
>
ist" <[EMAIL PROTECTED]>
Sent: Monday, December 01, 2003 8:18 AM
Subject: Re: [DbUtils]Making the BeanHandler... Even Smarter
> One goal of DbUtils is to not become a "framework". IMO, this feature is
> creeping towards framework status. Using an SQL "AS" is
You can do it with strings too:
private static String FIELD_LIST = " column1 as beanProp1, column2 as
beanProp2,
column3 as beanProp3 ";
String sql1 = "SELECT" + FIELD_LIST + "FROM ... ";
I use this way:
"SELECT ${FIELD_LIST} FROM ... ";
I think it can be better to use this map for any
One goal of DbUtils is to not become a "framework". IMO, this feature is
creeping towards framework status. Using an SQL "AS" is simpler and
clearer than writing Java code which forces you to maintain information
about your queries in two separate places, needlessly complicating things.
It's t
.k.a Mungo Knotwise of Michel Delving
"One ring to rule them all, one ring to find them..."
> -Original Message-
> From: Corby Page [mailto:[EMAIL PROTECTED]
> Sent: Sunday, November 30, 2003 9:01 PM
> To: [EMAIL PROTECTED]
> Subject: [DbUtils]Making the BeanHandler..
I am finding that my DAOs that use the BeanHandler are ending up with a lot
of code like this:
String queryName = "select column1 as beanProp1, column2 as beanProp2,
column3 as beanProp3"
This gets to be very redundant and clunky for large rows, and it happens
because DbUtils assumes that the
