Re: Dreaming About Redesigning SQL

From: Mikito Harakiri (mikharakiri_at_iahu.com)
Date: 10/15/03 

Date: Tue, 14 Oct 2003 17:51:27 -0700

"Daniel Parker" <danielaparker@windupbird.com> wrote in message
news:5g0jb.6483$PM2.621645@news20.bellglobal.com...
> With languages like Java and C# that support reflection, it is so easy to
do
> dynamic binding between a class and a SQL result set, matching properties
by
> name to result set column values, that this is not the relevant
> consideration.

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?

Relevant Pages

  • Re: Dreaming About Redesigning SQL
    ... reflection provides you with iteration over class fields. ... > my design is overwhelmed with reflection that indicates that I would ...
    (comp.object)
  • Re: Accessing object properties
    ... Kevin wrote: ... you can manipulate it through reflection -- Type.GetPropertyand friends should do the trick. ... The point of LINQ to SQL is to bridge the gap between objects and tables by allowing strongly-typed access to the underlying database. ...
    (microsoft.public.dotnet.languages.csharp)
  • RE: Data Access
    ... Someone has already written some code to use reflection and custom attributes ... to dynamically build the required SQL. ... > execute the stored procedure. ... > when there are say 30 form fields that need to be inserted or updated. ...
    (microsoft.public.dotnet.general)