design patterns - Database Abstraction - what are the options? -
How can I restrict my database to my application so that it is unaware of the database type? I have to design a .NET 3.5 WPF application, which is to support SQL Server or Visual FoxPro as a data repository.
My design goals are:
- Type the data invisible data repository
- switch between SQL and FoxPro while writing code in the Data Access layer Do not make as quick and painless as possible to do
- Allow the use of both ANSI SQL and stored procedures DL
- To learn for other developers joining the project At least the state Ahia
It is using will have a WPF application, perhaps Sisela.
I have thought of using any type of ORM but there is no experience with such technology. Many ORM database types are agnostic, although FoxPro requirement can restrict your choises or you Needs to be typed. Own provider or adapter
If you want your app to be able to work with multiple database types, then through the configuration, you should be careful that your schema is consistent in every database and you depend on those features Which are not implemented in any of the databases or ORMs you have selected.
The ORM I am most familiar with LLBL Gene Pro supports 5 or 6 back-end databases, but FoxPro is not officially supported by a customer contributing to the FoxPro adapter at one point. I do not know that it has been maintained.
Comments
Post a Comment