No, this is definitely not the reason in my case as I can reproduce this
issue on every 3.7.2/3.7.3 machine I've tested after copying the
database file (and only the database file) to these machines.
Am 15.11.2010 15:41, schrieb Kirk Clemons:
> Not sure if it helps but I would see this quite fre
to
know why integrity_check doesn't find the error before making a backup.
(What means that a bug exists in any case: either in PRAGMA
integrity_check or in the backup function).
---
Pirmin Walthert
Am 16.11.2010 14:22, schrieb Black, Michael (IS):
> Sorry, I meant .dump
>
> Given
to
know why integrity_check doesn't find the error before making a backup.
(What means that a bug exists in any case: either in PRAGMA
integrity_check or in the backup function).
---
Pirmin Walthert
Am 16.11.2010 14:22, schrieb Black, Michael (IS):
> Sorry, I meant .dump
>
> Given
l D. Black
> Senior Scientist
> Advanced Analytics Directorate
> Northrop Grumman Information Systems
>
>
>
>
> From: sqlite-users-boun...@sqlite.org on behalf of Pirmin Walthert
> Sent: Tue 11/16/2010 6:27 AM
> To: sqlite-users@sqlite.
No, this is definitely not the reason in my case as I can reproduce this
issue on every 3.7.2/3.7.3 machine I've tested after copying the
database file (and only the database file) to these machines.
Am 15.11.2010 15:41, schrieb Kirk Clemons:
> Not sure if it helps but I would see this quite fre
here are sensitive informations
stored inside and changing anything in the database seems to fix the
error! => Normally deleting one single row, not depending on from what
table, fixes the error... So it will be hard to delete the sensitive
information while keeping the error.
---
Pirmin Walthert
Am 1
a record normally helps (no matter what record from what table)
- on every machine the database file was working for a while after the
upgrade to 3.7.2 and after a few changes (inserts, updates and deletes)
it became "unbackupable"
Pirmin
Am 12.11.2010 20:30, schrieb Pirmin Walthert:
Am 12.11.2010 14:40, schrieb Pirmin Walthert:
> Am 12.11.2010 14:19, schrieb Black, Michael (IS):
>> Do a "sum" on the files to make sure they are identical.
>>
>> #1 Show all the files in the directorty
>> #2 How are you copying?
>>
>> Basically..
; Michael D. Black
> Senior Scientist
> Advanced Analytics Directorate
> Northrop Grumman Information Systems
>
>
>
>
> From: sqlite-users-boun...@sqlite.org on behalf of Pirmin Walthert
> Sent: Fri 11/12/2010 6:42 AM
> To: sqlite-users@sqlite.
Am 12.11.2010 13:06, schrieb Simon Slavin:
> On 12 Nov 2010, at 7:55am, Pirmin Walthert wrote:
>
>> Some months ago we changed to uclibc-git (nptl support), kernel
>> 2.6.32.X, busybox> 1.16 and at the moment sqlite 3.7.2.
> Are you accessing your databases straight from
is platform without any troubles (samba, php, openvpn, asterisk and
many others) and the uclibc-developers are discussing about making a
0.9.32 release based on this code during the next weeks.
Best regards,
Pirmin Walthert
___
sqlite-users mailing list
s
11 matches
Mail list logo