Last post Mar 24, 2006 11:23 AM by Double
Mar 24, 2006 11:23 AM|Double|LINK
Hi people !
Before I'll know the Data Access Applicantion Block, I implemented my own Data Access Helper class, it's simple only instanciates the DDBB connections and prepares DataAdapters.
But now knowing Data Access Application Block I believe prefer to implement it, because looks more completly. But I need clarify why uses some solution strategies in their methods:
- ¿ Why needs pass every time the connection on the DAAB, in each method ? ¿why not DAAB automate connection?
- ¿ Why we can't send and sqlCommand object (typed storeProcedured) with their parameters included, and not mounting on DAAB ?
- ¿ It's shared/static class, can't not inherits ... only oriented on SQLServer ? ¿Can be transformed for multi Data phisical Repositoris?
- ¿ Ussing multiple repositories, for example SQLServer, Oracle and XML, what next ilustration is recomended ussing DAAB ? ¿and with out ussing DAAB ?
DAL (SQL) <---> | | <---> | SQLServer |
DAL (Oracle) <---> | DAAB | <---> | Oracle |
DAL (XML) <---> | | <---> | XML |
| DAAB (SQL) | <---> | SQLServer |
DAL (Generic) <---> | DAAB (Oracle) | <---> | Oracle |
| DAAB (XML) | <---> | XML |
| | <---> | SQLServer |
DAL (Generic) <---> | DAAB (Generic) | <---> | Oracle |
| | <---> | XML |
(*) I think the last, but if DAAB its only for SQLServer then It's confussing me.