Re: creating ExecuteQuery method
- From: Marc Gravell <marc.gravell@xxxxxxxxx>
- Date: Thu, 20 Mar 2008 17:23:45 -0700 (PDT)
Other thoughts:
* might want to think about "struct" T, or discount it with T : class;
as it stands it will be boxed repeatedly and changed discared. Would
need "object foo = t" after create, and use foo (not t) in SetValue
* if you don't use T : class, might want to think about T =
Nullable<TSomethingElse>; here new(T) = null...
* might want to ignore readonly properties
* might want to think about a mapping attribute between SQL column
name and the object property name
Who said ORM was easy? ;-p
.
- Follow-Ups:
- Re: creating ExecuteQuery method
- From: Andrus
- Re: creating ExecuteQuery method
- References:
- creating ExecuteQuery method
- From: Andrus
- Re: creating ExecuteQuery method
- From: Marc Gravell
- Re: creating ExecuteQuery method
- From: Marc Gravell
- Re: creating ExecuteQuery method
- From: Andrus
- Re: creating ExecuteQuery method
- From: Marc Gravell
- Re: creating ExecuteQuery method
- From: Andrus
- Re: creating ExecuteQuery method
- From: Marc Gravell
- Re: creating ExecuteQuery method
- From: Andrus
- creating ExecuteQuery method
- Prev by Date: Re: creating ExecuteQuery method
- Next by Date: Re: Master / Detail w/ IList
- Previous by thread: Re: creating ExecuteQuery method
- Next by thread: Re: creating ExecuteQuery method
- Index(es):
Loading