DI can be used for several ends.
Imagine you have this application that must support different SQL server engines like:
- SQL Server
- Oracle
- MySQL
- PostgreSQL
- Sybase
- SQLite
- DB2
This not just a problem a connection strings and stored procedures. For example, SQLite has no stored procedures and your CRUD methods need to be different.
What you need is your application to load a different module for every (or only for some) SQL engine. ObjectBuilder can take care of that.
The problem is how the CSLA data portal will handle it.
To be continued
Copyright (c) Marimer LLC