This question is locked. New answers and comments are not allowed.
I have two databases with entirely different schema but both serve the same business vision. One is MsSql based and the other is MySql based. For example, there is an employee table. They exist in both the databases but with different schemas. I don't have to make two different UI because for the end user because the data come from both the databases are the same.
I'm looking at leveraging OpenAccess for this project. I have few questions which someone can answer:
1. I dont want to create any new stored procedures. Does the inline sql queries make the data access layer slow with OpenAccess?
2. Because I have two database backends, I have to create two different dataaccess layers - one for mssql and the other one for mysql. That looks ugly. Can I have just one data access layer with OpenAccess and divert the queries to mssql db or mysql db. The client will tell what database has to be used.
3. Can I create just a domain model with OpenAccess and keep the data access layer seperate? This may be better design because I have a domain and the UI can work on that domain. I assume OpenAccess needs a database as a start.
I appreciate the feedback.
I'm looking at leveraging OpenAccess for this project. I have few questions which someone can answer:
1. I dont want to create any new stored procedures. Does the inline sql queries make the data access layer slow with OpenAccess?
2. Because I have two database backends, I have to create two different dataaccess layers - one for mssql and the other one for mysql. That looks ugly. Can I have just one data access layer with OpenAccess and divert the queries to mssql db or mysql db. The client will tell what database has to be used.
3. Can I create just a domain model with OpenAccess and keep the data access layer seperate? This may be better design because I have a domain and the UI can work on that domain. I assume OpenAccess needs a database as a start.
I appreciate the feedback.