Design guide-lines for writing a Typed SQL Statement API ?
Posted
by this. __curious_geek
on Stack Overflow
See other posts from Stack Overflow
or by this. __curious_geek
Published on 2010-04-06T07:58:08Z
Indexed on
2010/04/06
8:03 UTC
Read the original article
Hit count: 191
Last night I came up to sometihng intersting while designing my new project that brought me to ask this qustion here.
My project is supposed to follow Table Gateway pattern using tradional ADO.Net datasets for data access. I don't want to write plain queries in my data-access classes. So I came up with an idea of writing a parser kindaa api that exposes objects and methods to generate queries on the move based on my domain objects.
Later I want this api to hook up to my Business objects and provide Typed SQL generator api right on the business object instances.
Any idea or references how can I do this ? This seems very wide to start with that I'm compelled take your opinions here. Does there anything already exists that can do this ?
© Stack Overflow or respective owner