Max Vlasov ha scritto:
On Fri, Dec 18, 2009 at 6:27 PM, Gianandrea Gobbo go...@solari.it wrote:
Gianandrea, I once had an experience with fixing a modified code that led to
database disk image malformation. If you can reproduce the bug with a
comparatively few number of steps, I'd recommend
On 21 Dec 2009, at 8:00am, Gianandrea Gobbo wrote:
At this stage, I cannot think of an applicative bug that leads to this
kind of corruption, where the database results always in the same size.
The only time I ever saw a number of files all truncated to the same length,
the fault was in
I also using 2.8, but i wondering why your database has 200 kb from the
beginning. my databases have only 3 or 4 kb's. But at my host if i am
using sqlite queries which are $db- like, i get the same error. funny
thing, but the database is not malformed...
On 18 Dec 2009, at 3:27pm, Gianandrea
I'm using sqlite (2.8) on an embedded product, running a Linux kernel.
I'm experiencing sometimes a database corruption, and listing some
tables contents gets me a SQL error: database disk image is malformed.
Ok, there can be many reasons for this, but the strange thing that
puzzles me is that
On 18 Dec 2009, at 3:27pm, Gianandrea Gobbo wrote:
I'm using sqlite (2.8) on an embedded product, running a Linux kernel.
I'm experiencing sometimes a database corruption, and listing some
tables contents gets me a SQL error: database disk image is malformed.
Ok, there can be many reasons
On Fri, Dec 18, 2009 at 6:27 PM, Gianandrea Gobbo go...@solari.it wrote:
I'm using sqlite (2.8) on an embedded product, running a Linux kernel.
I'm experiencing sometimes a database corruption, and listing some
tables contents gets me a SQL error: database disk image is malformed.
Ok, there
