On Fri, 2010-01-22 at 20:07 +0100, Federico Di Gregorio wrote: > On 22/01/2010 19:33, Jonathan Pryor wrote: > > The theory was that you could still get Mono's System.Data.Linq to > > communicate with non-SQL Server databases by using special parameters in > > the connection string (e.g. the DbLinqProvider value [0]), but recent > > bugs indicate that this approach doesn't work with PostgreSQL, as they > > throw an error on all unrecognized values. > > What? This was my first patch to dblinq and we're using dblinq with > connecton strings (cleaning connection string to be sure npgsql does not > receive anything extra). jonp, can you please point me to a test case > that shows how this does not work?
Behold! http://code.google.com/p/dblinq2007/issues/detail?id=177 The above reports two issues: (1) that in some circumstances Npgsql is upper-casing the connection string keys (resulting in "DBLINQPROVIDER", which isn't matched by our regex), and (2) newer versions of Npgsql reject DbLinqProvider altogether. Not having a PostgreSQL server to try to reproduce with, the above is all I have to go one, but it's apparently hit at least one person. - 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.
