John LeSueur wrote:
Maybe it's the principle of least surprise. As a new
developer, coming to sqlite, if there was this reference counting and
loosely emulated nested transactions, and one
day I made a mistake and called sqlite3_begin() twice and calling
sqlite3_end() just once, nothing would be
Kervin L. Pierre wrote:
Hello,
These functions are not supposed to
be replace nested transactions. They
just use the tools the API *already*
has to make it easier to work with
transactions in recursive and
inter-dependent functions/methods.
sqlite3_rollback() would rollback the
transaction. It doe
In users experience, what is the most stable,
supported LGPL ( or free'er ) SQLite wrapper
library out there?
I've seen
http://www.sqlite.org/cvstrac/wiki?p=SqliteWrappers
LiteSQL seems like the strongest contender.
http://litesql.sourceforge.net/
Any preferences? Input?
Thanks,
Kervin
On Fri, 2005-04-01 at 15:11 -0500, G. Roderick Singleton wrote:
> On Fri, 2005-04-01 at 14:37 -0500, D. Richard Hipp wrote:
> > On Fri, 2005-04-01 at 09:06 -0500, G. Roderick Singleton wrote:
> > > Running make test as a normal user, make test halts in wait() at the
> > > following test:
> > >
> >
On Fri, Apr 01, 2005 at 01:56:16PM -0500, Ned Batchelder wrote:
> I decided for my own work that magic nested transactions are a bad idea. To
> properly handle errors and rollback the database, you need to know where the
> edges of the transaction really are. Fully-supported nested transactions
Hello,
These functions are not supposed to
be replace nested transactions. They
just use the tools the API *already*
has to make it easier to work with
transactions in recursive and
inter-dependent functions/methods.
sqlite3_rollback() would rollback the
transaction. It does nothing else.
By you c
On Fri, 2005-04-01 at 14:37 -0500, D. Richard Hipp wrote:
> On Fri, 2005-04-01 at 09:06 -0500, G. Roderick Singleton wrote:
> > Running make test as a normal user, make test halts in wait() at the
> > following test:
> >
> > lock-2.1... Ok
> > lock-2.2... Ok
> > lock-2.3.1... Ok
> > lock-2.3.2...
On Fri, 2005-04-01 at 11:54 -0800, [EMAIL PROTECTED] wrote:
> The fix is to NOT disable twolevel namespaces, but to fix SQLite's
> Makefile.in to not hoark the linking of the testfixture.
Patches for Makefile.in will be cheerfully accepted.
--
D. Richard Hipp <[EMAIL PROTECTED]>
On Apr 1, 2005, at 11:10 AM, Stephen C. Gilardi wrote:
For several months now, I've gotten similar errors when I run the
test on my PowerBook G4. For me, the set of tests that fail is
different from test run to test run, but they do seem to be
concentrated in the "*ioerr" tests for the most
On Fri, 2005-04-01 at 09:06 -0500, G. Roderick Singleton wrote:
> Running make test as a normal user, make test halts in wait() at the
> following test:
>
> lock-2.1... Ok
> lock-2.2... Ok
> lock-2.3.1... Ok
> lock-2.3.2... Ok
> lock-2.4.1... Ok
> lock-2.4.2... Ok
> lock-2.5... Ok
> lock-2.8...
>
Ned Batchelder wrote:
I went through this same issue in my application, and realized that
rollbacks throw off the whole scheme. This proposal doesn't account for
rollbacks: how would they work? If only the outermost "transaction" would
truly perform a rollback, then what would an inner one do?
For several months now, I've gotten similar errors when I run the test
on my PowerBook G4. For me, the set of tests that fail is different
from test run to test run, but they do seem to be concentrated in the
"*ioerr" tests for the most part.
I've run the test several times on a G5 PowerMac an
I went through this same issue in my application, and realized that
rollbacks throw off the whole scheme. This proposal doesn't account for
rollbacks: how would they work? If only the outermost "transaction" would
truly perform a rollback, then what would an inner one do?
Consider this scenario
That is? excuse but creed not to have understood your participation... :)
However I have resolved my problem that was a syntax error of which
I did not succeed to understand of the reason then but... I have
resolved
Hi Max
Martins Mozeiko ha scritto:
And now tell us, which part of your proble
That's a good question. It would save all the wrapper writers some
time. I don't think the library is the place to put thread safe
code for several reasons:
Some of us don't use threads and don't need thread
safe code.
I prefer modular code with as little mixing of function
as possible. It makes i
> >>Please note that the SQL standard does not prohibid stable sorting
> >>outcome.
> >
> >It does prohibit it. It states the output is not sorted unless
> >you ask for it to be.
> >
> May I ask, are you a lawyer?
No. As a programmer you must be just as vigilant about following
the rules as a lawy
> But why should he have to? This is not a dumb idea, Jay. We are told
> that sqlite3_exec is for "legacy code support", which means that the
> only recommended option must be to use sqlite3_prepare/step/final for
> transactions. That's a fair bit of code (plus error checking) to put
> in
> every
On Fri, 2005-04-01 at 17:30 +0200, Steven Van Ingelgem wrote:
> Hi,
>
> When I was using 2.8, i could do the following:
>
> BEGIN ON CONFLICT IGNORE;
>
> As of v3 it seems this is gone?
>
> Is there any way to achieve the same, but not to add it to EVERY query in the
> transaction?
>
The ON
Jay wrote:
The begin and end functions could be configured
to begin/end the transaction *if* there isn't/is
one.
Dumb idea?
Do I get get to wear the dunce hat? :)
You should really look at an object oriented language.
You can do exactly this very simply.
But why should he have to? This
Jay wrote:
OK, there is no requirement, but there is a wish to return a stable
sorting outcome.
Just add an 'order by' clause.
Please note that the SQL standard does not prohibid stable sorting
outcome.
It does prohibit it. It states the output is not sorted unless
you ask for it to be
Hi,
When I was using 2.8, i could do the following:
BEGIN ON CONFLICT IGNORE;
As of v3 it seems this is gone?
Is there any way to achieve the same, but not to add it to EVERY query in the
transaction?
Thanks,
Steven
> The begin and end functions could be configured
> to begin/end the transaction *if* there isn't/is
> one.
> Dumb idea?
> Do I get get to wear the dunce hat? :)
You should really look at an object oriented language.
You can do exactly this very simply.
>
> OK, there is no requirement, but there is a wish to return a stable
> sorting outcome.
Just add an 'order by' clause.
> Please note that the SQL standard does not prohibid stable sorting
> outcome.
It does prohibit it. It states the output is not sorted unless
you ask for it to be.
> Plea
Running make test as a normal user, make test halts in wait() at the
following test:
lock-2.1... Ok
lock-2.2... Ok
lock-2.3.1... Ok
lock-2.3.2... Ok
lock-2.4.1... Ok
lock-2.4.2... Ok
lock-2.5... Ok
lock-2.8...
What is supposed to happen? Last time I had failed tests the solution
was run as user.
These are some helpful links to read.
Re: data type info:
http://www.sqlite.org/datatype3.html
http://www.sqlite.org/cvstrac/wiki?p=DateAndTimeFunctions
http://www.sqlite.org/cvstrac/getfile/sqlite/doc/affinity.html
SQL as understood by Sqlite:
http://www.sqlite.org/lang.html
Re: API functions (
Team,
Iam new to SQL-Lite, have finished reading the documentation. I would
like list of data types and common functions offered by the database.
Does any one know of comparison reviews between open source databases ?
- Goutam
*
And now tell us, which part of your problem relates to SQLite? :)
--
Martins
From: SKORPIO-INFO [EMAIL PROTECTED]
Date: Fri, 1 Apr 2005 15:17:56 +0300
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] Query select
> ok :)
>
> I have resolved this problem:
>
> SLOT_SEARCH = BSS.execute("SE
ok :)
I have resolved this problem:
SLOT_SEARCH = BSS.execute("SELECT * FROM slot WHERE
data_slot='01-04-2005' AND ((num_slot > "+str(contatore[1])+") AND
(num_slot < "+str(contatore[0])+"))")
Thanks
SKORPIO-INFO ha scritto:
Hi to all,
I have the necessity to carry out a query that it must find
Hi to all,
I have the necessity to carry out a query that it must find an
occurrence to me in which the date is x and that a data field is
comprised between y and z
This is the example:
contatore = [20,33]
SLOT_SEARCH = BSS.execute("SELECT * FROM slot WHERE
data_slot='01-04-2005' AND ((num_slot
Hi, it's just the final tested rlease of SQLITE 2.X MANAGER.
Requires Flash Player 7 plug in for Internet Explorer and if you need to
manage on-line sqlite 2.X files you need to configure and upload a
unique php5 file and your host must be copatible with php5.
Sorry for last emails and if anyone
30 matches
Mail list logo
