Hi,
thanks for the clarification. I may need to add a custom
implementation of the VFS or a patch for the -shm files to be held on
memory-disk then.
Regarding the question, why I want to wrap reads in a transaction is,
because I don't know if there'll be a write as part of the transaction
in befo
If you have some time for that, I'd appreciate patching at least fts2. This
will make it possible for Chromium to drop another custom patch for SQLite.
On Wed, Aug 18, 2010 at 13:49, Richard Hipp wrote:
> I'm thinking that you shouldn't be using FTS1 and FTS2 in the first place.
> They are untes
Reads to not write to the WAL. But they might write to the shared-memory.
On Thu, Sep 16, 2010 at 1:16 PM, Martin C. wrote:
> Hi,
>
> I am using SQLite on a NAND based embedded system, and to ensure the
> lifetime of the NAND I need to optimize writes to the NAND.
>
> Can you tell me, if a read
Just curious why you wrap your SELECT statement into a 'TRANSACTION' ...
-Original Message-
From: sqlite-users-boun...@sqlite.org
[mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Martin C.
Sent: quinta-feira, 16 de setembro de 2010 14:16
To: sqlite-users@sqlite.org
Subject: [sqlite]
Hi,
I am using SQLite on a NAND based embedded system, and to ensure the
lifetime of the NAND I need to optimize writes to the NAND.
Can you tell me, if a read-only transaction, by which I mean
BEGIN TRANSACTION
SELECT * from SomeTable;
COMMIT
will cause any writes to the WAL?
What abou
On Wed, Sep 15, 2010 at 06:00:40PM -0700, Cory Nelson scratched on the wall:
> SQLite doesn't support automatic indexing,
It does as of 3.7.
-j
--
Jay A. Kreibich < J A Y @ K R E I B I.C H >
"Intelligence is like underwear: it is important that you have it,
but showing it to the wron
ok, I think I'll use the snapshot in the mean time. Thank you
Il 16/09/2010 15.43, Richard Hipp ha scritto:
> On Thu, Sep 16, 2010 at 9:02 AM, Michele Pradella<
> michele.prade...@selea.com> wrote:
>
>> After some days of test the application work fine and with VMMap I see
>> small value of m
On Thu, Sep 16, 2010 at 9:02 AM, Michele Pradella <
michele.prade...@selea.com> wrote:
> After some days of test the application work fine and with VMMap I see
> small value of mapped file and I see only 1 instance of -shm allocated,
> some times 2 but it's all ok. So I'll wait for the next amalg
After some days of test the application work fine and with VMMap I see
small value of mapped file and I see only 1 instance of -shm allocated,
some times 2 but it's all ok. So I'll wait for the next amalgamation
release to have an official sources for that fix.
When do you think will be releas
You know, compilers are like women - they warn you about a lot of
things you really don't need to worry about.
On 16/09/2010 12:18, Dan Kennedy wrote:
> On Sep 16, 2010, at 2:09 AM, jagjeet singh nain wrote:
>
>> Hi,
>> I was compiling sqlite on 64 bit OS and i got following warning
>> message.
On Sep 16, 2010, at 2:09 AM, jagjeet singh nain wrote:
> Hi,
> I was compiling sqlite on 64 bit OS and i got following warning
> message.
>
> sqlite3.c: In function 'rtreeInit':
> sqlite3.c:118698:20: warning: cast from pointer to integer of
> different size
> Two versions were tried, 3.6.23.
jagjeet singh nain schrieb:
> Hi,
> I was compiling sqlite on 64 bit OS and i got following warning message.
Its probably an issue of:
http://www.sqlite.org/faq.html#q17
Michael
--
Michael Schlenker
Software Architect
CONTACT Software GmbH Tel.: +49 (421) 20153-80
Wiener Straße 1-3
Hi,
I was compiling sqlite on 64 bit OS and i got following warning message.
sqlite3.c: In function 'rtreeInit':
sqlite3.c:118698:20: warning: cast from pointer to integer of different size
Two versions were tried, 3.6.23.1 and 3.7.2 but both had same warning message.
Default configuration script
13 matches
Mail list logo
