On 2011-05-24 18:37, Ruth Ivimey-Cook wrote: > So far the create database thing is my bugbear. It doesn't seem hard or > bad practice to implement "create database" as a no-op (or better, an > expunge of the current file so that the app sees an empty database). > > I guess a workaround could be to modify the wrapper to search/replace > create database out of existence... that really does seem like a hack!
According to this: http://msdn.microsoft.com/en-us/library/bb399375%28v=VS.90%29.aspx you need to create a class for your database that inherits from DataContext. CreateDatabase is a DataContext method. So it looks to me like you need to override that method in your derived database class. This is just from poking around on MSDN. I am no doubt terribly wrong, and will now be mocked. Look at the testlinq program and see how it connects. Maybe that will give you some pointers. Joe D _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
