-- Zbigniew Baniewski <[EMAIL PROTECTED]> wrote: > The problem is, that the error message actually gives not any clue. It just > tells, that "there was problem while truing to open temporary database file" > - but there (considering the above) shouldn't be any problem. /var/tmp has > rwxrwxrwx privileges. Even worse: it's working without any problems most of > the time - and then, after f.e. a week, it refuses to work any further, > without any particular reason. It did open that temporary files 100 times > before - and it can't open it at 101. time.
What happens on the 102nd time? If it fails, then it's easy enough to debug. Just put some debugging code in sqlite3UnixTempFileName() and find out what the problem is. > Perhaps there are other possible reasons, not just wrong permissions for > "temp" sub-dir? > > I think, that the error code should be more communicative, and there should > be something like "wrong permissions", "directory not found" or at least kind > of numerical error code added, to allow the reason of the problem be found. See also: http://sqlite.org/capi3ref.html#sqlite3_extended_result_codes ____________________________________________________________________________________Ready for the edge of your seat? Check out tonight's top picks on Yahoo! TV. http://tv.yahoo.com/ ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
