> --- "Sills, Adam" <[EMAIL PROTECTED]> wrote: > > The goal of our abstracted data classes were to give us the > ability, if > > necessary (and I doubt it will ever be necessary), to > rewrite the data layer > > for any data source, and have the business layer not know > the difference, > > and to provide very simple access to get at your data. Both
> The whole 'changing the data store' gets me. I hear it a lot > from OR mapping people. How often > are you realistically going to do this? Is it really worth > the effort? Bearing in mind switching > enterprise class databases is a costly and time-consuming > affair even when you don't take into > account redevelopment of code. Its not over-engineering if you are a software vendor that requires a DB. Unfortunately your clients can have a hand in dictating the RDBMS to sue. That's the case with my client right now. They have supported ORACLE for years but a new customer of theirs insisted on SQL server... Their sales guys also like the fact that they can sell the flexibility. Jim You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
