).
https://xkcd.com/2249/
scnr
Bye
--
Luca Olivetti
Wetron Automation Technology http://www.wetron.es/
Tel. +34 93 5883004 (Ext.3010) Fax +34 93 5883007
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi
7 it never happened.
Bye
--
Luca Olivetti
Wetron Automation Technology http://www.wetron.es/
Tel. +34 93 5883004 (Ext.3010) Fax +34 93 5883007
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailma
El 15/10/16 a les 19:49, Jens Alfke ha escrit:
On Oct 15, 2016, at 7:42 AM, Luca Olivetti wrote:
Instead of an autoincrement you could increment it manually in, say, 1000
increments.
Then, when you have to insert something between 1000 and 2000 you just use 1500.
Unfortunately this breaks
alled ID) that is auto-increment.
Instead of an autoincrement you could increment it manually in, say,
1000 increments.
Then, when you have to insert something between 1000 and 2000 you just
use 1500.
Bye.
--
Luca Olivetti
Wetron Automation Technology http://www.wetron.es/
Tel. +34 93 5883004
www.wired.com/2015/11/null/>
Obligatory xkcd reference
https://xkcd.com/327/
SCNR
Bye
--
Luca Olivetti
Wetron Automation Technology http://www.wetron.es/
Tel. +34 93 5883004 (Ext.3010) Fax +34 93 5883007
ds m_db null and will not call
> sqlite3_close.
Unless the second thread is called between the copy and the null assignment.
I think that these concurrent accesses should be protected by a critical
section.
Bye
--
Luca Olivetti
Wetron Automatización S.A. http://www.wetron.es/
Tel. +34 93 5883004
pascal is alive and kicking and highly portable:
http://www.freepascal.org
Bye
--
Luca Olivetti
Wetron Automatización S.A. http://www.wetron.es/
Tel. +34 93 5883004 (Ext.133) Fax +34 93 5883007
___
sqlite-users mailing list
sqlite-users@sqlite.org
htt
d package it
from scratch.
Check your distribution site for instructions on how to build an rpm
(e.g, for mandriva it is at
http://wiki.mandriva.com/en/Development/Howto/RPM)
Bye
--
Luca Olivetti
Wetron Automatización S.A. http://www.wetron.es/
Tel. +34 9
h "--enable-threadsafe" ?
Btw, you shouldn't hijack an existing thread for a new topic, use the
"Compose" or "New" button in your mail program, hitting "Reply" then
changing the subject will still show your message in the original thread
in any well beh
En/na Luca Olivetti ha escrit:
> En/na Dennis Cote ha escrit:
>> The original corruption may well have been caused by omitting the thread
>> safe option on the version of SQLite you were using.
>
> Pheew, I hope it is really so.
A quick follow-up: everything has been wo
o recover a
database. It's a pity, because with 3.3.8 (and, as you say, 3.2.7) it
appeared to work.
Bye
--
Luca Olivetti
Wetron Automatización S.A. http://www.wetron.es/
Tel. +34 93 5883004 Fax +34 93 5883007
___
sqlite-users mailing list
sq
En/na Jeff Brown ha escrit:
> But I need to be able to use it as a server with at
> most 10 clients that occasionally use the system.
Hi, I'm a newbie myself, so I didn't use the following, but did you check
http://www.sqlite.org/cvstrac/wiki?p=SqliteNetwork
?
Bye
--
Luca
En/na Luca Olivetti ha escrit:
>> I don't believe that there is any reason to expect a vacuum to correct a
>> corrupt database.
>
> Ah, ok, I thought that it did (at least it did with 3.3.8).
Side note: it wasn't actually completely corrupted (hard corruption c
En/na Dennis Cote ha escrit:
> Luca Olivetti wrote:
>
>> Well, I posted all the error messages I got back from sqlite, as well as
>> the snippet of code I use to execute all my queries, but I can post more
>> details if it can be useful (I'd only need to know which
ges I got back from sqlite, as well as
the snippet of code I use to execute all my queries, but I can post more
details if it can be useful (I'd only need to know which details could be).
Bye
--
Luca Olivetti
Wetron Automatización S.A. http://www.wetron.es/
Tel. +34 93 5883004 Fax
En/na Luca Olivetti ha escrit:
> En/na Luca Olivetti ha escrit:
>
>> Hello,
>> I'm using sqlite 3.3.8 under linux (mandriva 2007.1).
>
> [...]
>
>> 1) is sqlite suitable when you have multiple threads accessing the same
>> database? Or should
En/na Luca Olivetti ha escrit:
> En/na Luca Olivetti ha escrit:
>
>> Hello,
>> I'm using sqlite 3.3.8 under linux (mandriva 2007.1).
>
> [...]
>
>> 1) is sqlite suitable when you have multiple threads accessing the same
>> database? Or should
En/na Jerry Krinock ha escrit:
> How can I manually lock the database using the C API? I can't find
> any "lock" function.
In think you could just execute a "BEGIN EXCLUSIVE" query, then do your
thing then execute a "COMMIT" (or a "ROLLBACK&
lite> vacuum;
sqlite> pragma integrity_check;
wrong # of entries in index fifo_referencias
wrong # of entries in index sqlite_autoindex_fifo_fis_1
Is this expected? If so, how can I fix these errors? (yes, I know that I
could dump and restore, but I need something more automated).
Bye
--
L
En/na Luca Olivetti ha escrit:
> Hello,
> I'm using sqlite 3.3.8 under linux (mandriva 2007.1).
[...]
> 1) is sqlite suitable when you have multiple threads accessing the same
> database? Or should I delegate the access in a single thread and
> serialize the queries from
SQLITE_MISUSE}
begin
FSQLiteReturnId:=sqlite3_reset(vm);
FLog.error('sqlite3_step: '+query+' '+SqliteReturnString);
finished:=true;
If FSQLiteReturnId=SQLITE_CORRUPT then
begin
FLog.Error('intent
21 matches
Mail list logo
