Hi again,
I am wondering if there is any performance benefit in *not* wrapping
multiple SELECT calls in a BEGIN/END transaction?
As I understand it, with wrapping:
BEGIN -- does nothing (yet)
SELECT1 -- creates a SHARE-ONLY lock on the DB
SELECT2 -- nothing extra
SELECT3 -- nothing extra
END -- c
Thanks guys. Perhaps docs could be updated in the _prepare_v2 section, to
mention the 'best practices' lifecycle of a statement in regards to commit
On 9 October 2013 04:08, Stephan Beal wrote:
> On Tue, Oct 8, 2013 at 9:58 PM, Petite Abeille >wrote:
>
> >
> > On Oct 8, 2013, at 8:10 PM, Ste
Hello all,
Many years ago, Igor mentioned that you should always reset/finalize any
prepared statements before calling COMMIT.
I am wondering, is this still true?
I have prepared SELECTs and INSERTs which have been step()'d, but not reset.
the SELECTs tend to be stepped until there is no more da
On 17/09/2007, John Machin <[EMAIL PROTECTED]> wrote:
> On 17/09/2007 1:07 PM, Joe Wilson wrote:
> > --- "D. Richard Hipp" <[EMAIL PROTECTED]> wrote:
> > I have been struggling with the performance of insertion in sqlite.
> >
> > Here we have a very simple case :
> >
> > A table
Hi Mike,
i have noticed that things take a lot longer if they aren't surrounded by a
BEGIN;
do work;
COMMIT;
does that make a difference for you?
Paul
On 09/08/07, mos <[EMAIL PROTECTED]> wrote:
> I'm building my first index on a large table using the "Create index
> ix_Main on Table1(StringFie
is implemented or an
> equivalent black-box model of how sqlite works. But since Igor is like
> the next authoritative guru here after drh himself, that explanation
> should be correct.
>
> Cheers,
> M. Manese
>
> On 8/9/07, Paul Harris <[EMAIL PROTECTED]> wrote:
> >
On 09/08/07, Paul Harris <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Can someone please explain why adding the auto_increment term seems to
> STOP the auto_increment behaviour?
>
> $ sqlite3
> SQLite version 3.3.17
> Enter ".help" for instructions
> sqlite&
Hi,
Can someone please explain why adding the auto_increment term seems to
STOP the auto_increment behaviour?
$ sqlite3
SQLite version 3.3.17
Enter ".help" for instructions
sqlite> .headers on
sqlite> create table abc (id integer auto_increment primary key, value text);
sqlite> insert into abc (v
On 08/08/07, Igor Tandetnik <[EMAIL PROTECTED]> wrote:
> Lee Crain <[EMAIL PROTECTED]> wrote:
> > Would a search for an 'a' return a different result than a search for
> > an 'A'?
>
> By default, yes.
>
> > SELECT * FROM table WHERE field1 = 'a';
> >
> > Vs.
> >
> > SELECT * FROM table WHERE field1
On 03/08/07, john s wolter <[EMAIL PROTECTED]> wrote:
> Wiki's. I have not used them myself. What's the general idea? Is there a
> form type that would be easy to use?
>
wikis are very easy to use. in short, its basically a "forum" where
people can write and store information in a form that c
On 03/08/07, Nikola Miljkovic <[EMAIL PROTECTED]> wrote:
> [In the message "Re: [sqlite] Re: Re: how do i declare and use variables in
> sqlite?" on Aug 3, 11:47, "Paul Harris" writes:]
> > > >> create temporary table vars (name text, value someth
i haven't been around long, but here's my 2c anyway,
i find the sourceforge forums hopeless, any time I need to look for
info on one of their projects, i end up looking through their mailing
list - where forum posts are automatically sent to anyway.
mailing lists are good for on-going issues.
wik
> >> create temporary table vars (name text, value something);
> >> --
> >> insert into vars set name="x", value=0;
> >> --
> >> ... where something = (select value from vars where name="x")...
> >>
> >
> > I tried doing this, but there doesn't seem to be a way to do the same
> > thing with an UPDA
On 03/08/07, Nikola Miljkovic <[EMAIL PROTECTED]> wrote:
> [In the message "[sqlite] Re: how do i declare and use variables in sqlite?"
> on Aug 2, 18:22, "Igor Tandetnik" writes:]
> > Chase <[EMAIL PROTECTED]> wrote:
> > > how do i declare and use variables in sqlite?
> >
> > You don't. You decla
On 03/08/07, James Dennett <[EMAIL PROTECTED]> wrote:
> > -Original Message-
> > From: Chase [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, August 02, 2007 12:39 PM
> > To: sqlite-users@sqlite.org
> > Subject: [sqlite] how do i declare and use variables in sqlite?
> >
> >
> > select 542 as x
Hi,
I wanted to get a LOG10() function in sqlite3, and I found the
extension-functions.tgz file in http://sqlite.org/contrib
I am using the all-in-one sqlite3.h/c version of sqlite3, and the
extension-functions files don't seem to fit at all.
For example, it wants to call a function called sqlit
Hi,
I wanted to get a LOG10() function in sqlite3, and I found the
extension-functions.tgz file in http://sqlite.org/contrib
I am using the all-in-one sqlite3.h/c version of sqlite3, and the
extension-functions files don't seem to fit at all.
For example, it wants to call a function called sqlit
17 matches
Mail list logo
