Data access layer design
Posted
by
Sam
on Stack Overflow
See other posts from Stack Overflow
or by Sam
Published on 2012-05-31T22:27:12Z
Indexed on
2012/05/31
22:40 UTC
Read the original article
Hit count: 114
I have a web app and a console application accessing a db. The db has 2 tables (A, B) one of which (A) is specific to the web app. When writing a data access layer, what is the best way to do it? Technically data access layer should provide access to all the data accessible. In doing so, methods to interact with A are exposed to the console application if we have single access layer. Does creating 2 access layers to 2 table in the same database makes any sense? What is a good way to do it?
© Stack Overflow or respective owner
