I am working on the constructor for DataContext(connectionString).
It turns out that I need two pieces of information in the code: the
IDbConnection class, and IVendor class.
In order to make it simpler for the user, I thought that I would add a
method to IVendor along the lines of
"IDbConnection CreateDbConnection(string connString);" - then only
one piece of information would be supplied by the user (IVendor) and
the other one could be deduced.
I expected to implement this in each IVendor, e.g. like this:
public IDbConnection CreateDbConnection(string connectionString)
{
return new
System.Data.Sqlite.SqliteConnection(connectionString);
}
But implementing this function is made harder by the fact that
DbLinq.Sqlite does not have a reference to System.Data.SqlLite.dll -
contrary to my expectations.
Is this a design goal - to have a lightweight provider DLL?
Is it okay for me to add this reference (same change in Oracle
provider etc), or should I do it differently?
Cheers, Jiri
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"DbLinq" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/dblinq?hl=en
-~----------~----~----~----~------~----~------~--~---
