Hi Pascal, Pascal Craponne wrote: > Hi, glad to read from you again. > > I'm not sure I get your point, so I explain more mine: > 1. All vendors are in the System.Data.Linq.csproj. All as internal. > 2. The public parts are exactly the same as they are in MS Linq, and we > don't care here. > 3. The trick is just that we find a way (somehow) to guess the vendor > given a IDbConnection or a connection string (I'm more pessimistic about > the last one). > Where's the mistake above?
Ahh, OK, I was under the impression that other DB vendors than SQL Server support won't go into System.Data.Linq.csproj (right now only DBLinq.SqlServer is there). So, it is 1 :) So, it won't block "identify by connection string" approach once we get other vendors there. It could be also done for IDbConnection by identifying its type i.e. "guess vendor by IDbConnection type". I guess that's easier, especially considering that .ctor( IDbConnection,...) is already implemented ;-) Atsushi Eno --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
