On Tue, Jul 24, 2018 at 5:11 PM Simon Slavin wrote:
> On 24 Jul 2018, at 11:34pm, J Decker wrote:
>
> > If the system rebooted; did a screen size change, and terminated the
> > program, it's possible it coild cause corruption.
>
> Step 1: use the command-line tool to fix your existing
On 24 Jul 2018, at 11:34pm, J Decker wrote:
> If the system rebooted; did a screen size change, and terminated the
> program, it's possible it coild cause corruption.
Step 1: use the command-line tool to fix your existing corruption.
Step 2: prevent more corruption.
Ignoring the possibbility
On Tue, Jul 24, 2018 at 1:47 PM Simon Slavin wrote:
> On 24 Jul 2018, at 8:43pm, J Decker wrote:
>
> > I have a database that got corrupted; was working on implementing
> automatic
> > recovery
>
> It would be a million times better to figure out how the corruption occurs
> and prevent it.
On 24 Jul 2018, at 8:43pm, J Decker wrote:
> I have a database that got corrupted; was working on implementing automatic
> recovery
It would be a million times better to figure out how the corruption occurs and
prevent it.
Simon.
___
On 7/24/18, J Decker wrote:
>
> I have a callback configured on SQLITE_CONFIG_LOG
> sqlite3_config( SQLITE_CONFIG_LOG, errorLogCallback, 0);
>
> Which is global, and does not identify the instance. I figured, I could
> just easily register the same callback on the db connection object
>
>
I have a database that got corrupted; was working on implementing automatic
recovery
I have a callback configured on SQLITE_CONFIG_LOG
sqlite3_config( SQLITE_CONFIG_LOG, errorLogCallback, 0);
Which is global, and does not identify the instance. I figured, I could
just easily register the
6 matches
Mail list logo
