I have been bitten by this a couple of times, so now I'm super-conservative
about how I deal with this.
What I do is have any parent database setup done by having the parent spawn
a child process to do the actual database work, and return any data the
parent needs in the status or (if more than a
On Fri, 15 Nov 2019 at 16:10, Graham Holden wrote:
> I've been having problems with my email system... I don't think
> earlier attempts at sending have made it to the list, but if they
> did, apologies for any duplication...
>
> Monday, November 11, 2019, 5:46:05 PM, Jukka Marin
> wrote:
>
> >>
On 15 Nov 2019, at 8:03am, Graham Holden wrote:
> What I *think* this may mean is that re-spawned children will inhereit
> the open file-handle of the SQLite connection opened by the parent
> after it initially fired all child processes.
That's not a problem.
> Even if the (re-spawned)
> child
I've been having problems with my email system... I don't think
earlier attempts at sending have made it to the list, but if they
did, apologies for any duplication...
Monday, November 11, 2019, 5:46:05 PM, Jukka Marin wrote:
>> On 11 Nov 2019, at 5:13pm, Jukka Marin wrote:
>>
>> > The main pr
Just to make sure, you didn't oversee that (like I was ...):
Daemonizing a process is also a fork() - and this invalidates
your connection!
I used the daemon() function in my program (together with a
few other processes) that used a DB connection. I opened
this connection _before_ I called daemon
On Mon, Nov 11, 2019 at 05:37:37PM +, Simon Slavin wrote:
> On 11 Nov 2019, at 5:13pm, Jukka Marin wrote:
>
> > The main process first opens the databases and checks that their
> > version matches that of the software and if not, the databases are
> > closed and initialized by running a scrip
On 11 Nov 2019, at 5:13pm, Jukka Marin wrote:
> The main process first opens the databases and checks that their
> version matches that of the software and if not, the databases are
> closed and initialized by running a script.
>
> After closing the databases, main process forks the children and
On Mon, Nov 11, 2019 at 05:03:25PM +, Simon Slavin wrote:
> On 11 Nov 2019, at 1:42pm, Jukka Marin wrote:
>
> > Or does the main process need to close all databases, then fork, then
> > reopen the databases?
>
> Which processes access the databases ? The main process ? Its children ?
> A
Doing the latter - closing everything, forking, re-opening - is always
going to be safe. Or if the parent isn't going to use the connection, just
don't open the database until you're in the child after forking.
On Mon, Nov 11, 2019 at 8:08 AM Jukka Marin wrote:
> On Fri, Nov 08, 2019 at 09:57:25
On 11 Nov 2019, at 1:42pm, Jukka Marin wrote:
> Or does the main process need to close all databases, then fork, then
> reopen the databases?
Which processes access the databases ? The main process ? Its children ? Are
they all using the same connection ? Are they all trying to use the same
On Fri, Nov 08, 2019 at 09:57:25AM +0200, Jukka Marin wrote:
> On Thu, Nov 07, 2019 at 09:26:46AM -0800, Shawn Wagner wrote:
> > This line stood out:
> >
> > > The main process opens the databases and then forks the other processes
> > which can then perform database operations using the already o
On Thu, Nov 07, 2019 at 09:26:46AM -0800, Shawn Wagner wrote:
> This line stood out:
>
> > The main process opens the databases and then forks the other processes
> which can then perform database operations using the already opened
> databases.
>
> From
> https://sqlite.org/howtocorrupt.html#_ca
This line stood out:
> The main process opens the databases and then forks the other processes
which can then perform database operations using the already opened
databases.
From
https://sqlite.org/howtocorrupt.html#_carrying_an_open_database_connection_across_a_fork_
:
> Do not open an SQLite d
Dear List,
I'm developing software which keeps parameters and real-time data in
SQLite databases on a x86_64/linux system. I am getting "database
disk image is malformed" errors from SQLite when using select. Some
select operations succeed, some fail. This happens on multiple systems.
I would
On 6 Oct 2017, at 1:55pm, Fahad wrote:
> I can now reliably corrupt my database - and this happens only when some
> other process is writing to the database while I perform sqlite3_close_v2 on
> the connections.
Reliable corruption will help investigation tremendously. To help investigate
this
I can now reliably corrupt my database - and this happens only when some
other process is writing to the database while I perform sqlite3_close_v2 on
the connections. I'll explain what I'm doing.
Since the last I wrote, I've disabled all the flags other than these:
#define SQLITE_ENABLE_FTS3 1
#d
27 AM
To: sqlite-users@mailinglists.sqlite.org
Subject: Re: [sqlite] 'database disk image is malformed' only on the mac
I don't think so:
https://sqlite.org/threadsafe.html
"With -DSQLITE_THREADSAFE=2 the threading mode is multi-thread." Setting it
to 0 disables all mutex
I don't think so:
https://sqlite.org/threadsafe.html
"With -DSQLITE_THREADSAFE=2 the threading mode is multi-thread." Setting it
to 0 disables all mutexes (assumes single threaded)
So I've set it to be multi-threaded.
Okay so I've wrapped @synchronized(..) around my database usage, stopped
cach
>#define SQLITE_ENABLE_FTS3 1
>#define SQLITE_OMIT_DEPRECATED 1
>#define SQLITE_OMIT_SHARED_CACHE 1
>#define SQLITE_OMIT_AUTOMATIC_INDEX 1
>#define SQLITE_OMIT_DECLTYPE 1
>
>#define SQLITE_DEFAULT_MMAP_SIZE 0
>#define SQLITE_DEFAULT_MEMSTATUS 0
>#define SQLITE_DEFAULT_SYNCHRONOUS 1
>
>#define SQLIT
On 09/21/2017 04:20 AM, Fahad wrote:
Thanks Jens, yes I didn't take the warnings from the Thread Sanitizer
lightly. Although I'm very confident with the actual implementation (using
thread local dictionaries) and have verified time and again using unit tests
that my code is otherwise thread-safe,
On Wed, 20 Sep 2017 06:41:05 -0700 (MST), Fahad
wrote:
[...]
> 1) Thread A: Create a new connection, if one already does not exist for the
> thread. Store it's 'reference count' in the thread storage (I close a
> connection when the count becomes zero).
> 2) Thread A: Get a previously stored stat
Thanks Jens, yes I didn't take the warnings from the Thread Sanitizer
lightly. Although I'm very confident with the actual implementation (using
thread local dictionaries) and have verified time and again using unit tests
that my code is otherwise thread-safe, I really do think there are perhaps
ce
No I'm not.
--
Sent from: http://sqlite.1065341.n5.nabble.com/
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
Fahad,
Are you calling sqlite3_wal_checkpoint_v2?
Brian Macy
On Sep 20, 2017, 1:59 PM -0400, wrote:
>
> I've run the Thread Sanitizer with my own SQLite-based on macOS, and haven't
> seen any warnings in sqlite3.c. So what you got could be a real warning sign.
_
> On Sep 19, 2017, at 8:20 PM, Fahad wrote:
>
> I recently switched on the Thread Sanitizer in Xcode only to find that it
> was complaining of race conditions inside of the sqlite3.c code, that the
> various readers and writers were trying to read / write to the same
> wal-index.
I've run the
I've tried that as well. Since I'm using PRAGMA journal_mode=WAL on all the
connections, I've had issues with MMAP (as acknowledged by the threads
above) so have had to disable that. I also need FTS 3 to work.
The rest of the flags to do with synchronisation and threading, I've enabled
/ disabled
I apologise for the many posts, but I'm writing in hope that one of you may
point out something that I'm either doing wrong, or a concept I haven't
fully grasped.
I'm aware that prepared statements are tied to the database connection they
were created for. In order to get more speed out of my rec
I can't be certain now but I think this thread is related:
http://sqlite.1065341.n5.nabble.com/Re-Database-corruption-and-PRAGMA-fullfsync-on-macOS-td95366.html
It was this thread that I landed on earlier this year to presumably fix the
issues I was experiencing personally. This did help, in fact
On 20 Sep 2017, at 4:20am, Fahad wrote:
> These are the flags I've finally settled on:
Revert all those settings. Allow SQLite to use its default settings. See if
that makes your problem go away.
This is purely for testing. Once you know whether it works or not you can
start setting them
Hi Dan
The plugin I'm referring to is a 'Share' plugin that one can embed inside of
a mac app, which then shows up in the "Sharing" menu in Safari. When you
click on it, it launches in its own process, allowing you to share the
currently viewed website with your main app. Thus, the main app and th
On 09/15/2017 10:38 AM, Fahad wrote:
I tried it with sqlite3_shutdown(), didn't help. I was able to reproduce it
again using the main app and the safari share plugin.
You don't need to call sqlite3_shutdown(). All it does is release the
resources allocated by sqlite3_initialize() - which are t
On 15 Sep 2017, at 2:24pm, Fahad wrote:
> #define SQLITE_ENABLE_STAT4 1
Should not affect your problem.
> I also changed this:
>
> #define SQLITE_DEFAULT_WAL_AUTOCHECKPOINT 1000
>
> to 250
That may affect your problem. Try extreme values, with the objective being to
trigger definite corr
Hi Simon
Wanted to chime in to say I was able to in fact cause the database to go
corrupt from other external processes trying to write to the database (in
WAL mode) while the main app was also using the database. So I have a
feeling it's something else. I've tried hard to create a mini-app that
d
On 15 Sep 2017, at 4:38am, Fahad wrote:
> How can I prevent this from happening? Like I said, using a unit test I was
> able to reproduce this 1 out of 20 tries but when using the real app and
> plugin at the same time, I am able to reproduce every 5th try (it seems the
> app is opening / using
Hi Simon
I tried it with sqlite3_shutdown(), didn't help. I was able to reproduce it
again using the main app and the safari share plugin.
Main App: Finished writing to db, just opened a new connection to read
(after opening a connection I set PRAGMA query_only=1; PRAGMA
read_uncommitted=1; and r
On 18 Aug 2017, at 12:30am, Fahad G wrote:
> I do not have a way to reproduce this just yet, but I've been seeing way too
> many diagnostic logs from customers where their databases are being corrupt
> primarily on the Mac (the exact same code is shared between a Mac app, iPhone
> and iPad) pa
Hi
Although I've read all the rules (and am otherwise aware of what it takes to
report a bug), I want to apologise upfront. I do not have a way to reproduce
this just yet, but I've been seeing way too many diagnostic logs from customers
where their databases are being corrupt primarily on the M
On 1 May 2016, at 2:39am, Igor Korot wrote:
> How do I recover the information?
Do you have a copy of that file from before you updated ? Can you run
integrity_check() on it ?
Simon.
Simon,
On Sat, Apr 30, 2016 at 10:12 PM, Simon Slavin wrote:
>
> On 1 May 2016, at 2:39am, Igor Korot wrote:
>
>> How do I recover the information?
>
> Do you have a copy of that file from before you updated ? Can you run
> integrity_check() on it ?
IIUC, this file didn't change. It contains
Hi,
I just updated my system along with the compiler from 4.x to 5.2.
And now I start receiving the aforementioned errors trying to start
Anjuta.
I tried to open the db file with sqlite3 - it opens, but running
"PRAGMA integrity_check" it immediately gives:
igor at IgorDellGentoo ~/.cache/anjuta
Had another damaged database report.
This time it is a configuration database which holds application settings.
The file is stored on a local disk, not shared, and only ever accessed by my
application and only by one thread.
The database is run in FULL sync mode for maximum security.
I’m p
On Fri, 30 Jan 2015 13:17:26 -0500
Stephen Chrzanowski wrote:
> 2.1 Filesystems with broken or missing lock implementations
>
> SQLite depends on the underlying filesystem to do locking as the
> documentation says it will. But some filesystems contain bugs in their
> locking logic such that the
As I wrote above, damaged databases are replaced. No user continues working
with a damaged database once it has been identified. The issue here is to
detect this early and avoid it altogether.
> One column of one row of one table may get corrupted.
> If that's the case then the database ca
1. No client-server, I use MySQL, SQL-Server or ORACLE for that.
2. No access to the SQLite database ever by more than one process concurrently
in writable mode. In readable mode, yes. But the reported damage cases were
always single user, one PC.
3. I cannot prevent or disallow users to
I estimate that over 90% of the users keep the database on local disks. I can
tell from the log files.
Keeping the SQLite database it on a network server really hurts performance.
That’s not what SQLite is designed for, besides all other aspects of network
locking mentioned in various SQLite do
On Fri, Jan 30, 2015 at 8:07 AM, Mario M. Westphal wrote:
>
> When a user encounters the problem he/she restores the last working
> backup. I have a few users who faced this problem more than once. Here I
> always assumed some hardware glirch, a shaky USB connection, disk trouble,
> network probl
On 30 Jan 2015, at 1:07pm, Mario M. Westphal wrote:
> What worries me more are the incidents where users see this problem happen
> several times, with q database kept on a local hard disk or SSD.
Just to make it clear, when corruption is reported, the corruption is not
automatically fixed. T
> Okay. First, stop doing VACUUM after this. You're not improving things and
> you may be making things worse
Not important. If this error is encountered the database is marked and the user
reminded on every open/close to replace it with a backup. The database is not
supposed to be used af
On 2015/01/30 14:45, Mario M. Westphal wrote:
- The databases in question are stored on a location hard disk or SSD.
- If a user stores his database on a NAS box or Windows server, it is accessed
directly, via standard Windows file system routines.
- From what I can tell, network-based databa
On Fri, Jan 30, 2015 at 1:45 PM, Mario M. Westphal wrote:
> - From what I can tell, network-based databases are not more likely to
> corrupt than databases stored on built-in disks or SSDs or databases kept
> on disks or USB sticks connected via USB.
>
That's a big assumption. Network filesystem
- The databases in question are stored on a location hard disk or SSD.
- If a user stores his database on a NAS box or Windows server, it is accessed
directly, via standard Windows file system routines.
- From what I can tell, network-based databases are not more likely to corrupt
than database
On 29 Jan 2015, at 7:04pm, Mario M. Westphal wrote:
> The diagnosis log of my application reports the output of integrity_check()
> already.
>
> I retrieved the log from the most recent error report. This is my application
> has logged:
>
> '*** IN DATABASE MAIN ***
> ON TREE PAGE 385120 CEL
On Thu, Jan 29, 2015 at 2:07 PM, Mario M. Westphal wrote:
> Most database damaged errors encountered over time could be pinned to
> power failures, disk or *network problems*.
>
>
Network problems? I might have missed a good chunk of this thread, but,
this begs to be asked Are you runnin
The core code is in place since about 2008.
I took advantage of changes in SQLite over time, from using the shared cache to
switching to WAL mode for databases which are not opened in read-only mode.
These changes were made between 12 and six months ago, and tested during beta
tests and als
The diagnosis log of my application reports the output of integrity_check()
already.
I retrieved the log from the most recent error report. This is my application
has logged:
'*** IN DATABASE MAIN ***
ON TREE PAGE 385120 CELL 24: INVALID PAGE NUMBER 151192068
CORRUPTION DETECTED IN C
My application does not phone home :-/ but I can add output of these functions
to the log file my application maintains. My users know how to collect these
log files and send them to me.
I will also add the error logging callback to my wrapper class and route it to
the log file.
This should
On 2015/01/28 20:06, Mario M. Westphal wrote:
1. I don’t have the damaged databases here so I cannot run the diagnosis
myself. The databases are usually too large to upload or transfer.
2. The SQLite version I currently use is 3.8.8.1 (complied using the Amalgation
and Visual Studio 2012).
Bu
On 1/28/15, Mario M. Westphal wrote:
> 1. I don’t have the damaged databases here so I cannot run the diagnosis
> myself. The databases are usually too large to upload or transfer.
>
> 2. The SQLite version I currently use is 3.8.8.1 (complied using the
> Amalgation and Visual Studio 2012).
> But
1. I don’t have the damaged databases here so I cannot run the diagnosis
myself. The databases are usually too large to upload or transfer.
2. The SQLite version I currently use is 3.8.8.1 (complied using the Amalgation
and Visual Studio 2012).
But since not every user always keeps up to day, ol
On 28 Jan 2015, at 3:15pm, Mario M. Westphal wrote:
> The damage is usually detected during “diagnosis” runs. This feature runs an
> “analyze” and a” vacuum” command in order to physically validate the database
> (and to optimize and compact it).
Please don't do that. Neither of those things
On Wed, Jan 28, 2015 at 4:19 PM, Richard Hipp wrote:
> On 1/28/15, Mario M. Westphal wrote:
> > Recently I get an increasing number of error reports about “database disk
> > image malformed” errors from my users. These errors show up out of the
> blue,
> > with databases held on local hard disks
On 1/28/15, Mario M. Westphal wrote:
> Hello,
>
>
>
> I’m using SQLite in one of my applications for several years with great
> success.
>
> The databases managed with SQLite are between 1 and maybe 10 GB, with about
> 50 tables or so.
>
> The platform is Windows 7 or higher.
>
>
>
> Recently I ge
Hello,
I’m using SQLite in one of my applications for several years with great success.
The databases managed with SQLite are between 1 and maybe 10 GB, with about 50
tables or so.
The platform is Windows 7 or higher.
Recently I get an increasing number of error reports about “database d
In my experience, retrying does often work.
-david
On Tue, Sep 25, 2012 at 7:31 PM, Rittick Gupta wrote:
> Do you think a retry of the query would help resolve this issue ? Do I
> have to close & reopen the database.
>
> Thanks for your help.
>
> regards,
>
> Rittick
> _
Do you think a retry of the query would help resolve this issue ? Do I have to
close & reopen the database.
Thanks for your help.
regards,
Rittick
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/s
Yes, still having that problem. We've moved to new servers with SSD's and a
ton of RAM, and that seems to have helped matters -- not sure why, though I
don't know why it was happening in the first place. (I'm *guessing* the
issue is due to two conflicting queries happening at the same time, so if
David,
Thanks. Do you still have the problem ? Did you find a workaround to
avoid the problem - appreciate your response.
regards,
Rittick
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqli
You might be interested in this thread:
http://www.theusenetarchive.com/usenet-message-sqlite-does-disabling-synchronous-and-shared-cache-cause-%22error-database-disk-image-is-malformed%22-20780199.htm
No conclusion was ever obtained, but the discussion was good.
-david
On Mon, Sep 24, 2012 at
I have a mult-threaded application. Each thread uses its own database handle.
One thread got a return value of 11 (disk image malformed) - with the
sqlite3_step statement (select statement). When we restarted the application
after the failure the database recovered and did not give any error.
W
On 23 Jan 2012, at 9:45am, Sreekumar TP wrote:
> -My journal mode is set to WAL, synchronous mode is NORMAL and Checkpoint
> mode is Manual.
>
> Transactions are written to the WAL file, therefore, even if the WAL file
> is lost, I should be able to retrieve the database without
> corruption.(sa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23/01/12 01:45, Sreekumar TP wrote:
> Transactions are written to the WAL file, therefore, even if the WAL
> file is lost, I should be able to retrieve the database without
> corruption.(sacrificing some data ofcourse) ?
Correct. A checkpoint w
-My journal mode is set to WAL, synchronous mode is NORMAL and Checkpoint
mode is Manual.
Transactions are written to the WAL file, therefore, even if the WAL file
is lost, I should be able to retrieve the database without
corruption.(sacrificing some data ofcourse) ?
Moreover, I do know that t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23/01/12 01:03, Sreekumar TP wrote:
> is it possible to find out if sqlite was in the middle of a transaction
> when the power off occurred ?
WAL mode has the transactions in a separate file. Normal mode alters the
database and keeps the original
Yes, this is a case of corruption. The problem occurred during a power
cycle test. I have the synchronous mode set to NORMAL.
By examining the header of the DB ,is it possible to find out if sqlite was
in the middle of a transaction when the power off occurred ?
-Sreekumar
On Mon, Jan 23, 2012
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23/01/12 00:13, Sreekumar TP wrote:
> What can I infer from these logs ?
Your database is corrupted. Here is a list of possible causes:
http://www.sqlite.org/howtocorrupt.html
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Lin
Hi,
I have get the following error when a sql statment is executed ( query ) -
"database disk image is malformed".
On running the quick_check pragma on the db, I get the following log -
"*** in database main ***
On tree page 1595 cell 5: Rowid 2104 out of order (max larger than parent
max of 206
I'm having the same problem with my application.
Basically, it's a combination of jukebox/music management app I've been
developing myself over the last few years. I had always used the dump
commands to back up & restore the database, given that I develop on both
linux and windows. When the bac
> -Original Message-
> From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-
> boun...@sqlite.org] On Behalf Of Dan Kennedy
> Sent: woensdag 9 februari 2011 19:26
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] database disk image is malformed 3.7.x
>
&
> I didn't find a way yet to reproduce the issue with a "clean" database.
> Only way I can reproduce it is with some of the database, like the
> test.db3. So I'm running out of ideas.
This is the theory. test.db3 is an auto-vacuum database.
http://www.sqlite.org/src/info/89b8c9ac54
Dan.
___
On 02/10/2011 12:10 AM, Dan Kennedy wrote:
> On 02/09/2011 08:17 PM, Dennis Geldhof wrote:
>> I checked some things for the attached database. It is created with
>> sqlite version 3.6.3 or 3.6.23.1 with the help of the system.data.sqlite
>> wrapper. The header displays (with the ./showdb) version 3
On 02/09/2011 08:17 PM, Dennis Geldhof wrote:
> I checked some things for the attached database. It is created with
> sqlite version 3.6.3 or 3.6.23.1 with the help of the system.data.sqlite
> wrapper. The header displays (with the ./showdb) version 3.7.4, so it is
> opened and changed with a datab
I checked some things for the attached database. It is created with
sqlite version 3.6.3 or 3.6.23.1 with the help of the system.data.sqlite
wrapper. The header displays (with the ./showdb) version 3.7.4, so it is
opened and changed with a database viewer tool. Before executing the
"query" the data
> -Original Message-
> From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-
> boun...@sqlite.org] On Behalf Of Dan Kennedy
> Sent: woensdag 9 februari 2011 5:57
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] database disk image is malformed 3.7.x
>
On 02/08/2011 10:24 PM, Dennis Geldhof wrote:
>> -Original Message-
>> From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-
>> boun...@sqlite.org] On Behalf Of Dan Kennedy
>> Sent: dinsdag 8 februari 2011 14:51
>> To: sqlite-users@sqlite.org
>>
> -Original Message-
> From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-
> boun...@sqlite.org] On Behalf Of Dan Kennedy
> Sent: dinsdag 8 februari 2011 14:51
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] database disk image is malformed 3.7.x
>
>
On 02/08/2011 08:26 PM, Dennis Geldhof wrote:
>> -Original Message-
>> From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-
>> boun...@sqlite.org] On Behalf Of Dan Kennedy
>> Sent: dinsdag 8 februari 2011 12:33
>> To: sqlite-users@sqlite.org
>>
> -Original Message-
> From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-
> boun...@sqlite.org] On Behalf Of Dan Kennedy
> Sent: dinsdag 8 februari 2011 12:33
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] database disk image is malformed 3.7.x
>
>
On 02/08/2011 06:00 PM, Dennis Geldhof wrote:
> Hi all,
>
>
>
> I experienced some strange behavior between different versions of
> sqlite. Our application uses the System.Data.Sqlite wrapper
> (http://sqlite.phxsoftware.com/) which is on sqlite version 3.6.23.1,
> but the tools we use to view the
Hi all,
I experienced some strange behavior between different versions of
sqlite. Our application uses the System.Data.Sqlite wrapper
(http://sqlite.phxsoftware.com/) which is on sqlite version 3.6.23.1,
but the tools we use to view the database are on sqlite version 3.7.4.
In the application n
2010/8/2 Yoni Londner :
> Hi,
> Actually it DOES help.
> I just found out that I ran the wrong executable.
> Sorry if I wasted your time :-)
> When will you have an official release of this version?
See planned date here:
http://sqlite.org/draft/releaselog/3_7_1.html
"SQLite Release 3.7.1 On 2010
Hi,
Actually it DOES help.
I just found out that I ran the wrong executable.
Sorry if I wasted your time :-)
When will you have an official release of this version?
Yoni.
On Mon, Aug 2, 2010 at 3:02 PM, Yoni Londner wrote:
> Hi Dan,
> Thanks for the response.
> I tried to new version, but the pr
Hi Dan,
Thanks for the response.
I tried to new version, but the problem still exist.
I continued to debug it, and found that the error detected in btreeInitPage
(on decodeFlags).
I also found that if i run without enabling shared cache, the problem does
not happen.
Hope that it will help.
Yoni.
O
On Aug 2, 2010, at 6:13 PM, Dan Kennedy wrote:
>
> On Aug 2, 2010, at 1:42 PM, Yoni Londner wrote:
>
>> Hi,
>> Forgot to mention that the inserting should be inside a
>> transactions, so
>> complete repro steps are:
>> 1. open sqlite connection.
>> 2. PRAGMA journal_mode=WAL
>> 3. PRAGMA synchron
On Aug 2, 2010, at 1:42 PM, Yoni Londner wrote:
> Hi,
> Forgot to mention that the inserting should be inside a
> transactions, so
> complete repro steps are:
> 1. open sqlite connection.
> 2. PRAGMA journal_mode=WAL
> 3. PRAGMA synchronous=full
> 4. PRAGMA temp_store=memory
> 5. sqlite3_enable
Hi,
Forgot to mention that the inserting should be inside a transactions, so
complete repro steps are:
1. open sqlite connection.
2. PRAGMA journal_mode=WAL
3. PRAGMA synchronous=full
4. PRAGMA temp_store=memory
5. sqlite3_enable_shared_cache(1)
6. begin transaction
7. while(1) loop - insert record
Hi,
I am getting "database disk image is malformed" error while using WAL.
To reproduce:
1. open sqlite connection.
2. PRAGMA journal_mode=WAL
3. PRAGMA synchronous=full
4. PRAGMA temp_store=memory
5. sqlite3_enable_shared_cache(1)
6. while(1) loop - insert records to a table.
7. after 15 seconds,
Hi,
I have an application running on Windows CE4.1 PDAs with SD cards.
Sometimes I have errors executing commands on database that are:
11-database disk image is malformed
This happens for example on table MSTBP executing "Delete From MSTBP".
Or inserting into it.
The strange thing is, that aft
It was a typo. I was setting fullsync when the correct pragma name is
fullfsync.
On Fri, Sep 26, 2008 at 9:50 AM, Jeffrey Rennie (レニー） <[EMAIL PROTECTED]>wrote:
>
> 2008/9/25 D. Richard Hipp <[EMAIL PROTECTED]>
>
>>
>> You are confusing the statement journal with the rollback journal.
>> The sta
2008/9/25 D. Richard Hipp <[EMAIL PROTECTED]>
>
> You are confusing the statement journal with the rollback journal.
> The statement journal has nothing to do with database recovery - that
> is the task of the rollback journal. So the statement journal can be
> deleted at will without damaging th
Sorry, mispost
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
1 - 100 of 117 matches
Mail list logo
