Joe Mistachkin wrote: > > Are you sure the application is loading the new DLLs and not some stale DLLs > leftover from before? >
Yes, i look with Visual Studio in the "Loading Modules" window. Path and version are correct (1.7.5) before I had installed only some 1.6 runtimes. Hopes I do all right with compilation (thank again for your step-by-step help) > > Yes, my test case works properly (the first time). The second time, all the > rows have already been added and the test case fails, which is still the > expected behavior. > Ok, now its getting really strange. > > The C# code for the test case is here (in the EFTransactionTest method): > > http://system.data.sqlite.org/index.html/finfo?name=testlinq/Program.cs > > One thing you may notice about the test case is that I try to add a total of > 15 rows to > the database. The first five rows are added, the second five rows are NOT > added (because they would violate the PRIMARY KEY constraint), and the final > five rows are also added. > > The test case verifies that all 10 rows that should be added are in fact > added. It also verifies that the appropriate exception is raised for the > PRIMARY KEY constraint violation. So you add all the 15 rows inside one transactionscope and with one context.SaveChanges() call? Perhaps it makes a difference if the contains violation is inside the 15 rows you try to add (row 10 is incompatible with row 2 for example) or If it is a contains violation with data already in DB. For my test I add a single row to the DB just before I doing my transaction. -- Joe Mistachkin _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
