Joe Wilson wrote:
So this machine's minimum timer resolution is 0.0155 seconds,
or 15.5 milliseconds.
XP box?
XP & timers: http://www.lochan.org/2005/keith-cl/useful/win32time.html
Martin
-
To unsubscribe, send email
Matt Froncek wrote:
I have a program generator that creates ORs in SQL nested. This causes a
stack overflow in SQLite. Has this been addressed or will it be? If so what
version was it addressed. I am not sure how to search for the answer to this
question.
You ought to post a schema and some sam
Can you post the schema of the tables in the SELECT?
--- Matt Froncek <[EMAIL PROTECTED]> wrote:
> I have a program generator that creates ORs in SQL nested. This causes a
> stack overflow in SQLite. Has this been addressed or will it be? If so what
> version was it addressed. I am not sure how to
--- [EMAIL PROTECTED] wrote:
> A double is sufficient to store the current time to with about
> 25 microseconds. If you use 'now' to get the current time, the
> date functions try to capture the current time to this precision.
> That is implemented in the os_XXX.c layer. It's system dependent.
>
Tom Olson <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I know that SQLite uses a 64-bit floating point type to store Julian date
> information. Is this accurate to the second or a fraction of a second?
>
> I was doing some testing and tried to format a date using strftime() method
> with the %f optio
Hello,
I know that SQLite uses a 64-bit floating point type to store Julian date
information. Is this accurate to the second or a fraction of a second?
I was doing some testing and tried to format a date using strftime() method
with the %f option and I was unable to find a date that kept any mi
I'm trying to implement the equivalent of the following sybase query in
sqlite, but I suspect I've got it wrong. Any help much appreciated,
jim
update tmpRR_ML_final
set id = case when a.CDRefSNP <> 'NR' then b.id
when a.CDRefSNP = 'NR'
and a.CDRefMoody
I have a program generator that creates ORs in SQL nested. This causes a
stack overflow in SQLite. Has this been addressed or will it be? If so what
version was it addressed. I am not sure how to search for the answer to this
question.
Sample SQL:
SELECT "SalesLine"."ROWID" AS "FQROWID", "Item
OK, thanks again.
-Original Message-
From: Igor Tandetnik [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 20, 2007 10:56 AM
To: SQLite
Subject: [sqlite] Re: Re: Looking for equivalent syntax
Anderson, James H (IT)
wrote:
> In order to improve my understanding, I'd like to ask 2 quest
Anderson, James H (IT)
wrote:
In order to improve my understanding, I'd like to ask 2 questions re
the
sql, below.
1. what is the relationship between the "select * from where" within
the
"where exists" and the "select yadayadayada from where" within the
set?
No direct relationship. However,
Christian Smith wrote:
> SQLite has been known to be problematic using NFS drives, mainly due
> to flaky NFS locking implementations.
I'm not sure it's fair to say SQLite is "problematic". It's susceptible
to NFS locking problems in certain situations, but so is any other app
which assumes tha
Excellent! I didn't realize that the "oid" existed! This is perfect.
Thanks for this!
Not directly. But every row has an implicit primary key that you can
refer to using (amongst other names) "oid". You can use a SELECT to
locate a single oid value and then use the oid to delete a single
row. i.
:)
On 2/20/07, P Kishor <[EMAIL PROTECTED]> wrote:
On 2/20/07, P Kishor <[EMAIL PROTECTED]> wrote:
> On 2/19/07, Jim Crafton <[EMAIL PROTECTED]> wrote:
> > If I have a simple table without an index column, and have multiple
> > rows with the same data, is it possible to *only* delete one row? In
In order to improve my understanding, I'd like to ask 2 questions re the
sql, below.
1. what is the relationship between the "select * from where" within the
"where exists" and the "select yadayadayada from where" within the set?
In other words, are they connected and if so, how?
2. why is it not
Allan, Mark uttered:
Hi,
A little while back I submitted a query as to whether SQLite would be a
good alternative to using MS Access as an internal database for a PC
application. I received many repiles for which I was grateful. Mostly
people thought that SQLite was a far more superior optio
On 2/19/07, Eric S. Johansson <[EMAIL PROTECTED]> wrote:
The application is an experimental anti-Spam testbed exploring the use
of reputation through proof for puzzles and user interaction. The list
of things I'm tracking is fairly significant (for me) and I'm trying to
pull things together.
Michael Schlenker <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> i noticed the note in the documentation that the implicit NOT NULL
> constraint for PRIMARY KEYs is currently not enforced by SQLite and
> wondered if there is an explicit way to set it?
>
> I expected specifying the NOT NULL explicitly
Hi all,
i noticed the note in the documentation that the implicit NOT NULL
constraint for PRIMARY KEYs is currently not enforced by SQLite and
wondered if there is an explicit way to set it?
I expected specifying the NOT NULL explicitly would work and enforce it,
but it does not:
CREATE
18 matches
Mail list logo