At 14:18 03/11/2005, you wrote:
As currently implemented, when an error occurs during
sqlite3_step(), the function returns SQLITE_ERROR. Then
you have to call either sqlite3_reset() or sqlite3_finalize()
to find the actual error code. Suppose this where to
change in version 3.3.0 so that the ac
Eduardo <[EMAIL PROTECTED]> wrote:
Isn't better lock the database while a transaction that can make a
SQLITE_SCHEMA error, as is done with writes? A change in database is
always a change. Also that way you don't waste time in rerunning the
affected transactions.
It is indeed locked as you descr
I've been using sqlite to ease making statistical graphs from
metrological data and have encountered a strange problem.
Two columns, 'rr' and 'slag', 'rr' contains precipitation and 'slag'
contains the type of precipitation as a two letter code. RR (capital)
is the code for rain, but any and all s
Bjørn Eikeland a écrit :
I've been using sqlite to ease making statistical graphs from
metrological data and have encountered a strange problem.
Two columns, 'rr' and 'slag', 'rr' contains precipitation and 'slag'
contains the type of precipitation as a two letter code. RR (capital)
is the code
On Nov 6, 2005, at 8:19 AM, Bjørn Eikeland wrote:
Two columns, 'rr' and 'slag', 'rr' contains precipitation and 'slag'
contains the type of precipitation as a two letter code. RR (capital)
is the code for rain, but any and all select statemens includeing
WHERE slag="RR" fails as it thinks I'm c
On 11/6/05, Puneet Kishor <[EMAIL PROTECTED]> wrote:
>
> On Nov 6, 2005, at 8:19 AM, Bjørn Eikeland wrote:
>
> > Two columns, 'rr' and 'slag', 'rr' contains precipitation and 'slag'
> > contains the type of precipitation as a two letter code. RR (capital)
> > is the code for rain, but any and all s
At 14:27 06/11/2005, you wrote:
Eduardo <[EMAIL PROTECTED]> wrote:
Isn't better lock the database while a transaction that can make a
SQLITE_SCHEMA error, as is done with writes? A change in database is
always a change. Also that way you don't waste time in rerunning the
affected transactions.
Eduardo <[EMAIL PROTECTED]> wrote:
Isn't better lock the database while a transaction that can make a
SQLITE_SCHEMA error, as is done with writes? A change in database is
first sqlite3_step succeeds, an implicit transaction is started
(I assume there are no explicit transactions i
Eduardo wrote:
At 14:27 06/11/2005, you wrote:
Eduardo
<[EMAIL PROTECTED]>
wrote:
Isn't better lock the database while a transaction that can make a
SQLITE_SCHEMA error, as is done with writes? A change in database is
always a change. Also that way you don't waste time in rerunning the
affected
Well, the write was an example. So, a lock_schema wouldn't do the
re-prepare, in some cases reparse, the other threaded transactions.
I don't quite follow how exactly this is supposed to help. Are you
saying that there should be some kind of a lock from the moment the
statement is pr
Eduardo wrote:
You seem to think that the problem occurs when schema changes right
in the middle of sqlite3_prepare call. This is not the case. The
problem is that a prepared statement may sit around for a long time
before it is actually used in a sqlite3_step call. At this point the
engine may f
Alexander Kozlovsky <[EMAIL PROTECTED]> wrote:
> Hi!
>
> I just notice, SQLite don't support this type of queries:
>
>
> select * from t1 where a >= ALL (select b from t2)
>
>
> Of course, queries with ALL, ANY and SOME clauses may be reformulated,
> but this is part of SQL standard.
>
>
On Sun, 06 Nov 2005 15:09:34 -0500, [EMAIL PROTECTED] wrote:
> Alexander Kozlovsky <[EMAIL PROTECTED]> wrote:
> > I just notice, SQLite don't support this type of queries:
> >
> >
> > select * from t1 where a >= ALL (select b from t2)
> >
> >
> > Of course, queries with ALL, ANY and SOME cl
> What are these constructs suppose to do?
x all (select y from t where ...)
is equivalent to
not exists (select y from t where not (x y) and ...)
Any and some are synonyms.
x any (select y from t where ...)
is equivalent to
exists (select y from t where x y and ...)
Any can be
Dave Dyer wrote:
>
> I looked into this, and the actual problem is windows returning
> a "access denied" error code when trying to recreate the journal
> file immediately after deleting it. I can't find any documentation
> that says create might fail for this reason, but filemon (from
> systemin
15 matches
Mail list logo
