Hi Donald, >> I think you're right for general purpose applications. But if you have ETL >> or data conversion/analysis applications that can be re-run after a failure >> (using source content), this type of pragma sounds like a reasonable choice.
> I very much agree with your statement -- I turn it off sometimes myself to > good effect. But the webpage will be read by all sorts of users, and there was not a mention of the conditions under which this would be wise or foolhardy. A newbie might well turn off synchronous inappropriately, take an application to production, then lose all her data. It just seems (to me at least) quite unfriendly not to include a warning when suggesting synchronous=OFF. My original question was very general - we are looking at using SQLite in many different scenarios - some like the traditional 'always on' application and some which are more backoffice type batch operations. I agree with concerns about not providing usage context to the discussion of pragmas. I'll make sure I provide this context in future pragma discussions. Regards, Malcolm _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
