M Mark Rae [MVP] Jan 29, 2008 #41 I don't have to change my DAL for any specific application. Click to expand... Me neither... I only change it if there is a TSQL change. Click to expand... I don't even have to do that...
I don't have to change my DAL for any specific application. Click to expand... Me neither... I only change it if there is a TSQL change. Click to expand... I don't even have to do that...
M Mark Rae [MVP] Jan 29, 2008 #42 How do you manage shifts between database servers or even other storage mediums (webservices, etc.) with this though? Click to expand... Factory pattern... IMO this is contrary to the purpose of abstraction as you are placing Data Access implementation details inside your BLL. Click to expand... My BLL interfaces with my DAL, never directly with the RDBMS... It's great if you only have one place in your BLL where that data is accessed, Click to expand... ??? My BLL interfaces with my DAL all over the place - everywhere it needs to, in fact... but what about cases where you need a different solution to retrieve your data Click to expand... Factory pattern...
How do you manage shifts between database servers or even other storage mediums (webservices, etc.) with this though? Click to expand... Factory pattern... IMO this is contrary to the purpose of abstraction as you are placing Data Access implementation details inside your BLL. Click to expand... My BLL interfaces with my DAL, never directly with the RDBMS... It's great if you only have one place in your BLL where that data is accessed, Click to expand... ??? My BLL interfaces with my DAL all over the place - everywhere it needs to, in fact... but what about cases where you need a different solution to retrieve your data Click to expand... Factory pattern...
