I had in mind that the IDbConnection.ConnectionString was a string, so it could be handled the same way... :)
On Tue, Mar 3, 2009 at 19:33, Jonathan Pryor <[email protected]> wrote: > On Tue, 2009-03-03 at 13:13 +0100, Pascal Craponne wrote: > > Regarding the fact of loading a given vendor, without referencing it, the > following threads were talking about it: > > > http://groups.google.com/group/dblinq/browse_thread/thread/9e3b0ffa5f2d7e1f/6716fb3496c10b5f > > > This seems to discuss the DataContext(string) constructor, which seems to > have been solved with the DbLinqProvider "parameter" within the connection > string (a useful solution). > > Alas, this seems to have no relevance to the DataContext(IDbConnection) > constructor. > > > http://groups.google.com/group/dblinq/browse_thread/thread/ce397e5f58b36a12/d7378bd1c401957a > > > > This also seems to be about the DbLinqProvider connection string parameter. > > However, it seems that I was blind, or at least not reading all the > sources; an appropriate DataContext constructor already exists within > src/DbLinq/Data/Linq/DataContext.Extended.cs: > > public DataContext(IDbConnection dbConnection, MappingSource > mappingSource, IVendor vendor) > > So we've already added an appropriate mechanism. My apologies for not > noticing this earlier. > > - Jon > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
