Suggest better way to implement dotConnect for various datasource
Posted: Sun 19 May 2013 05:34
Hi,
Currently I am using dotConnect ORM for PostgreSQL datasource in my app.
Planning to map our app to point to SQLLite datasource for few customers.
So planning to get dotConnect ORM for SQLLite too.
So please suggest an better way to implement both the datasource in single app.
The app shud not know which datasource to be called. It has to be decided runtime only.
We already has class decorated with [ProviderAttribute(typeof(Devart.Data.PostgreSql.Linq.Provider.PgSqlDataProvider))] attribute.
So is there a better way so that we don't generate code with SQLLite ORM object, Instead use the existing class. But the above attribute type has to be decided at runtime.
Please Suggest
Thanks,
Sathish
Currently I am using dotConnect ORM for PostgreSQL datasource in my app.
Planning to map our app to point to SQLLite datasource for few customers.
So planning to get dotConnect ORM for SQLLite too.
So please suggest an better way to implement both the datasource in single app.
The app shud not know which datasource to be called. It has to be decided runtime only.
We already has class decorated with [ProviderAttribute(typeof(Devart.Data.PostgreSql.Linq.Provider.PgSqlDataProvider))] attribute.
So is there a better way so that we don't generate code with SQLLite ORM object, Instead use the existing class. But the above attribute type has to be decided at runtime.
Please Suggest
Thanks,
Sathish