I suspect, although am not 100%, that a third-party database tool was using the database file. As you say, I would have expected either that tool or the actual program to have failed to open the file....
However, we could be a lot more sure if we could see the Win32 error. In the short-term I am going to add a modification to log this info whenever WriteFile() fails in the code mentioned, and will let you know if it is anything that looks suspicious. Out of interest, the file is on a local NT filesystem drive. Thanks, Steve -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 10 February 2006 17:28 To: [email protected] Subject: Re: [sqlite] Database Disk Full "Drew, Stephen" <[EMAIL PROTECTED]> wrote: >> > It's just a little bit misleading if you're not familiar with the > circumstances it's raised in... I've had some confused colleagues > wondering why their 100kb DB on a disk with 15gb free would be out of > space :) > I'm curious. What was preventing them from writing to the file if it was not a lack of disk space? File permission problems should have been detected when the file was opened. What else would cause a short write? -- D. Richard Hipp <[EMAIL PROTECTED]>
