Re: Dreaming About Redesigning SQL
From: Daniel Parker (danielaparker_at_windupbird.com)
Date: 10/15/03
- Next message: Shane Mingins: "Persistent Objects and ObjectLists"
- Previous message: JesseChen: "How to find my own design pattern"
- In reply to: Mikito Harakiri: "Re: Dreaming About Redesigning SQL"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 14 Oct 2003 21:20:53 -0400
"Mikito Harakiri" <mikharakiri@iahu.com> wrote in message
news:A_0jb.47$It5.208@news.oracle.com...
>
> Certainly, reflection provides you with iteration over class fields. But
if
> my design is overwhelmed with reflection that indicates that I would
better
> use collections of the fields from the start. What is the point
> encapsulating data if the main access path goes through reflection?
>
I don't understand this point. Why would the design be overwhelmed with
reflection? The only reflection logic would be in a single data query
utility class. The only design consideration is matching class property
names with aliased result set column names. It's a convenient way of
populating a data object with minimal code. You have to get the data in
there somehow anyway.
Regards,
Daniel Parker
- Next message: Shane Mingins: "Persistent Objects and ObjectLists"
- Previous message: JesseChen: "How to find my own design pattern"
- In reply to: Mikito Harakiri: "Re: Dreaming About Redesigning SQL"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
