try
my best to do it. :)
???:Simon Slavinslavins at bigfraud.org
???:SQLite mailing listsqlite-users at mailinglists.sqlite.org
:2016?1?14?(??)?20:39
??:Re: [sqlite] Database Corrupt While Disk Full
On 14 Jan 2016, at 11:55am, Brice Andr? brice.andre at ams-solutions.be wrote:
I
] Database Corrupt While Disk Full
On 14 Jan 2016, at 9:58am, sanhua.zh sanhua.zh at foxmail.com wrote: Through
the error code timeline, it shows that much of SQLITE_FULL, SQLITE_IOERR,
SQLITE_CANTOPEN happened before SQLITE_CORRUPT. You should never get to this
situation. The three result codes
On 2016/01/14 6:46 PM, R Smith wrote:
> ...// Out-of-memory and out-of-diskspace type errors are reported//
Also note here that there is a case where SQLite will report DISK_FULL
errors where the disks are seemingly fine - when you start a transaction
that requires large amounts of space,
On 2016/01/14 3:02 PM, sanhua.zh wrote:
> 1. Not all other codes except SQLITE_OK, SQLITE_ROW, SQLITE_DONE should be
> treated as fatal errors.
>As an example, SQLITE_BUSY indicates that this op is temporarily failed,
> but it can be done later. (Note that sometimes you should not retry
the database. Can you teach me a little
more in detail ? I haven?t found the relative code in SQLite source code.
???:Simon Slavinslavins at bigfraud.org
???:SQLite mailing listsqlite-users at mailinglists.sqlite.org
:2016?1?14?(??)?17:46
??:Re: [sqlite] Database Corrupt While Disk Full
Recently, my monitoring system showed that the error code SQLITE_FULL and
SQLITE_CORRUPT increasing in same trend. And thousands of users, who?s database
is corrupt, also traped inlow disk free space and their log show that
SQLITE_IOERR, SQLITE_FULL happenedsimultaneously.
I confuse that
On Thu, Jan 14, 2016 at 2:09 PM, Stephan Beal wrote:
> FULL means the drive is full. Most apps can't do much about that. It
> generally needs to be resolved by user action - freeing up space.
>
Alternately, FULL can mean that the current VFS cannot allocate space, even
though it's underlying
On Thu, Jan 14, 2016 at 2:02 PM, sanhua.zh wrote:
> I don?t mean to be rude. BUT, I can?t agree with your opinion, Simon.
>
>
> 1. Not all other codes except SQLITE_OK, SQLITE_ROW, SQLITE_DONE should be
> treated as fatal errors.
> As an example, SQLITE_BUSY indicates that this op is
On 14 Jan 2016, at 1:02pm, sanhua.zh wrote:
> I don?t mean to be rude. BUT, I can?t agree with your opinion, Simon.
I will present some arguments on my side. I hope you take this as cultured
conversation and not an outright rejection of your points.
> 1. Not all other codes except
Dear Simon,
I am a little worried with your last post because, I must admint that I do
not take special measures in my application when such errors occur to
guarantee that no more DB access are performed.
I have thus the following questions :
1. What would be the proper reaction to
> On 14 Jan 2016, at 11:55am, Brice Andr?
> wrote:
>
> I am a little worried with your last post because, I must admint that I do
> not take special measures in my application when such errors occur to
> guarantee that no more DB access are performed.
>
> I have thus the following questions :
On Thu, Jan 14, 2016 at 10:58 AM, sanhua.zh wrote:
> Through the error code timeline, it shows that much of SQLITE_FULL,
> SQLITE_IOERR, SQLITE_CANTOPEN happened before SQLITE_CORRUPT. Database
> might be in an obscure state while disk is full, then it corrupt in some
> unknown reason.
>
>
> As
On 14 Jan 2016, at 9:58am, sanhua.zh wrote:
> Through the error code timeline, it shows that much of SQLITE_FULL,
> SQLITE_IOERR, SQLITE_CANTOPEN happened before SQLITE_CORRUPT.
You should never get to this situation. The three result codes SQLITE_FULL,
SQLITE_IOERR, SQLITE_CANTOPEN are
On 14 Jan 2016, at 8:44am, sanhua.zh wrote:
> Recently, my monitoring system showed that the error code SQLITE_FULL and
> SQLITE_CORRUPT increasing in same trend. And thousands of users, who?s
> database is corrupt, also traped inlow disk free space and their log show
> that SQLITE_IOERR,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/01/16 00:44, sanhua.zh wrote:
> Recently, my monitoring system showed that the error code
> SQLITE_FULL and SQLITE_CORRUPT increasing in same trend.
Just as another data point, I had SQLite using code in a library that
was used across a bunch
15 matches
Mail list logo
