hello,
when I compile the amalgation with these compile
switches:SQLITE_OMIT_VIRTUALTABLEorSQLITE_OMIT_VIRTUALTABLE
the amalgation fails to compile: the implementation of some functions are
removed but the definition + call to these functions still exist. I use VS 2010
to compile. This is the
hello,
we have noticed that executing a select query in SQLite expert is 3 times as
fast as executing it using our own C++ application. This seems quite odd as we
are doing no funky stuff in the code, the sqlite3_step alone in our app takes
longer then the entire process in (compiling the
hi all,
I have the database set to fail in case of constraint violation. And it does
return SQLITE_CONSTRAINT from sqlite3_step when I try to insert/update an
invalid foreign key. But is there any way to find out exactly which constraint
failed as I might have many foreign key fields in the
hello all,
we have a database that only performs insert statements on a table (database
contains only this table), is it in this case a good idea to reduce the cache
size to, say, 5? Because if I understand things correctly the cache doesn't
really help you when you do nothing but inserts,
>
> > To: sqlite-users@sqlite.org
> > From: itandet...@mvps.org
> > Date: Thu, 20 Oct 2011 07:55:26 -0400
> > Subject: Re: [sqlite] string conatenated sql statements
> >
> > Gert Corthout <gert_corth...@hotmail.com> wrote:
> > > My argum
> To: sqlite-users@sqlite.org
> From: itandet...@mvps.org
> Date: Thu, 20 Oct 2011 07:55:26 -0400
> Subject: Re: [sqlite] string conatenated sql statements
>
> Gert Corthout <gert_corth...@hotmail.com> wrote:
> > My argument so far is that parametrized
hello,
I am looking at the data layer of my company's software and noticed we build
our queries with string concatenation (including user input). As a former
Oracle and SqlServer developer this sends shivers down my spine. I am trying to
convince management to get a budget for a switch to
hello,
we recently switched from SQLite version 3.5.4 to 3.7.5. When I run process
monitor on our machines I see a lot of failed file access attempts that weren't
there before (v 3.5.4).
It is failed QueryOpen (NAME NOT FOUND) events for DBASE-NAME.db3-wal and
DBASE-NAME.db3-journal.
I
8 matches
Mail list logo