On Fri, 2010-01-01 at 02:33 -0800, Matthijs de Z wrote: > maybe a stupid question, but since I've been googling around for the > last couple of days, I thought I might aswell ask you guys/girls.
Not a stupid question. The answer, however, may very well be stupid. Thus, the glib (potentially stupid) answer: DbLinq aims to implement the same public API as Linq-to-SQL. Consequently (in an ideal world), you should be able to use the MSDN System.Data.Linq documentation when programming against the public DbLinq.Data.Linq types. There will be exceptions to this, specifically the need for an IVendor (to specify which SQL dialect to use) and connections string extensions (which may themselves be broken as e.g. PostgreSQL is currently throwing errors if the connection string contains "unsupported" parameters), but that's the goal. Anyone up for writing actual documentation? ;-) - 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.
