DbLinq

The same way that every other vendor is tested, by downloading the software and generating the database from the sql-script. Specifically: del tests\northwind.db3 lib\sqlite3.exe -echo -init examples\DbLinq.SQLite.Example ... [More] \sql\create_Northwind.sql -bail tests\northwind.db3 .quit I don't feel it strongly, but I do think that *a* decision should be [Less]

SEND DETAILS FOR CLAIMS:NAME:SEX:LOCATION

That sounds horrible. - Jon

see [link] "•If you use the IGNORE keyword, errors that occur while executing the INSERT statement are treated as warnings instead. For example, without IGNORE, a row that duplicates an existing UNIQUE index or PRIMARY KEY value in the table causes a duplicate-key error and the statement is

I have no idea what an "insert ignore" statement is, but (assuming it's "standard" SQL) there's always DataContext.ExecuteCommand(): [link] This allows sending SQL directly to the DB with minimal DbLinq machinations.

Hi, is it possible to send an insert ignore statement to dblinq (based on a mysql database)? regards, Matthijs

Of course we'd still need the .db3 binary blob. How else do we easily test SQLite? ;-) That said, *please*, go forth and do it if you feel that strongly. It will require two things, though: 1. Updating documentation so that people attempting to ... [More] run the unit tests can actually have them pass. 2. Updating the unit tests themselves so that they pass. [Less]

I'm leaning that way. Including the *.db3 binary blob. You are right, that that there are more options with more data, rows could be added those missing cases. Issues like 195 and 196 are also hard to test with the current schema, but having few data, makes it easier to extend the schema. On the other hand, there are probably

Oddly, your message has "broken" message threading in Evolution... (Meaning that the message I'm replying to isn't shown as a reply to my previous message. Odd...) I did mention that I'm an idiot. Here's what happened: I saw "Northwind", assumed that it was the *actual* Northwind database, and when I was setting up my SQL Server

(I hope this isn't dupe, the interface accepted the message, but it didn't show up) Of course the test databases should contain the same data across vendors such that tests can be reused. And I didn't assume that the data in the "examples" ... [More] scripts is the same as in the "tests" scripts. But it seems that the data in the "examples" scripts is the same [Less]