nt is sometimes imperfectly executed, but it is my goal.
If that means that SQLite is uncompetitive, then so be it.
D. Richard Hipp
[EMAIL PROTECTED]
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
ze a GLOB where the right parameter is
a literal string. It will not do so if the right parameter is a
parameter. http://www.sqlite.org/optoverview.html#like_opt
D. Richard Hipp
[EMAIL PROTECTED]
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
ously here.
D. Richard Hipp
[EMAIL PROTECTED]
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
ng like 30 ms.
Tried to index also 'ModifiedDate' but it didn't help.
What am i doing wrong?
Thanks,
Ofir Neuman.
D. Richard Hipp
[EMAIL PROTECTED]
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
same database within the same process
and use them independently and locking should work correctly. You
should not have to change anything. It should just work.
D. Richard Hipp
[EMAIL PROTECTED]
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
connection. SQLite
contains its own mutexes to serialize access.
D. Richard Hipp
[EMAIL PROTECTED]
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
On Nov 19, 2007, at 12:36 PM, James Dennett wrote:
-Original Message-
From: John Stanton [mailto:[EMAIL PROTECTED]
Sent: Monday, November 19, 2007 7:36 AM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] Memory Usage
Not only applicable to real time systems. If you want a program to
system.
On Linux systems that typically use Doug Lea's malloc, there is
no measurable performance difference. But I have had some
people running embedded systems tell me that using the
malloc-free SQLite results in a significant speed boost. Your
mileage may vary.
D. Richard Hipp
[EMAIL PROT
erator precedence as the SQL standard
requires. If I am wrong about that, please correct me and I will
change it.
On the other hand, changing the operator precedence to agree with
MySQL or MSSQL is not something we are interested in doing if they
are using a non-standard precedence.
D. Richar
On Nov 17, 2007, at 5:12 PM, D. Richard Hipp wrote:
On Nov 17, 2007, at 4:58 PM, Joe Wilson wrote:
I'm having difficulty with Lemon's operator precedence.
That would be a bug in lemon...
I was wrong. Turns out the bug was in the SQLite grammar
file parse.y. It was assignin
NOT operator '~' have the highest precedence?
SQLite version 3.5.2
Enter ".help" for instructions
sqlite> select ~1 - ~5;
-8
sqlite> select (~1) - (~5);
4
That would be a bug in lemon...
D. Richard Hipp
[EMAIL PROTECTED]
-
l to [EMAIL PROTECTED]
------
---
D. Richard Hipp
[EMAIL PROTECTED]
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
, it is often
a good idea to run your GUI in a separate process from your
compute engine so that long computations don't free the display.
D. Richard Hipp
[EMAIL PROTECTED]
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
table implementation (other than the
ones
that are included with SQLite - such as FTS1-3) that will be broken
by an
API change, please let me know. And please also advice me how much of
a hardship a change would be for you.
D. Richard H
turn? 1, 2, or 3?
D. Richard Hipp
[EMAIL PROTECTED]
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
. Richard Hipp
[EMAIL PROTECTED]
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
ion
extension.
So it doesn't have an ECCN.
D. Richard Hipp
[EMAIL PROTECTED]
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
On Sep 2, 2007, at 1:13 PM, Miguel Fuentes wrote:
I didn't know .lib were much larger =\
I always use .a files, so my bad
I just linked it into my exe and got a final 420kb exe.
See also http://www.sqlite.org/cvstrac/wiki?p=SizeOfSqlite
D. Richard Hipp
[EMAIL PROT
n
future
releases. But until I better understand the backwards compatibility
issues,
I think it is probably better to leave it off for now.
D. Richard Hipp
[EMAIL PROTECTED]
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
e) so we probably will make the prebuilt libraries threadsafe
on all
platforms.
D. Richard Hipp
[EMAIL PROTECTED]
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
layer directly. For these reasons, calls directly
into the BTree layer are strongly discouraged.
--
D. Richard Hipp <[EMAIL PROTECTED]>
sult_error
at that point if it is appropriate to do so.
--
D. Richard Hipp <[EMAIL PROTECTED]>
c) that will emulate floating point.
(2) Modify the code to use integers rather than doubles to score
indices in the optimizer.
--
D. Richard Hipp <[EMAIL PROTECTED]>
On Tue, 2005-09-27 at 13:40 +0200, Joxean Koret wrote:
> Why not use mmap, munmap, mprotect, mlock, etc... system calls?
>
You ever tried to mmap a 10GiB database file into the memory
of processor with a 4GiB address space?
--
D. Richard Hipp <[EMAIL PROTECTED]>
You should not call sqlite3_result_* from within the step
function of an aggregate. Those routines may be called from
within the finalizer function only.
--
D. Richard Hipp <[EMAIL PROTECTED]>
SQLite version 3.2.7 is now available on the website.
This release fixes several obscure problems that were
discovered over the past week. There is no rush to
upgrade unless you are having problems.
--
D. Richard Hipp <[EMAIL PROTECTED]>
On Fri, 2005-09-23 at 13:00 -0400, Richard Nagle wrote:
> is there a easier way of typing in data to Sqlite.
>
> sqlite> insert into car (md_num, md_name, style, year)
> ...> values (1, 'Honda', 'Coupe', 1983)
> ...> ;
>
> Man, just 806 more listing
> just looking for some short cuts,
ithout this workaround.
>
> > -Original Message-
> > From: Jolan Luff [mailto:[EMAIL PROTECTED]
> > Sent: Saturday, September 17, 2005 4:14 PM
> > To: sqlite-users@sqlite.org
> > Subject: Re: [sqlite] Version 3.2.6
> >
> > On Sat, Sep 17, 2005 a
. Or you can get the patches
directly from http://www.sqlite.org/cvstrac/chngview?cn=2725.
--
D. Richard Hipp <[EMAIL PROTECTED]>
On Mon, 2005-09-19 at 15:19 -0400, D. Richard Hipp wrote:
> On Mon, 2005-09-19 at 19:36 +0200, Alain Bertrand wrote:
> > hi all,
> >
> > I am porting a program from mysql to sqlite.
> > The following statement doesn't work correctly with sqlite though it does
On Mon, 2005-09-19 at 16:06 -0400, Kervin L. Pierre wrote:
> D. Richard Hipp wrote:
> > Hence, the result set contains no rows. A COUNT() of a empty result
> > set gives NULL.
>
> I thought per the last discussion on "Sum and NULL"
> that the count of an empty
e.org/cvstrac/timeline and see if
you spot anything similar.
--
D. Richard Hipp <[EMAIL PROTECTED]>
photos.refid=pots.id
In this second join, the photos.kind=2 condition can never be met
because every row in the result of the previous join has photos.kind==1.
Hence, the result set contains no rows. A COUNT() of a empty result
set gives NULL.
--
D. Richard Hipp <[EMAIL PROTECTED]>
On Mon, 2005-09-19 at 13:42 -0400, D. Richard Hipp wrote:
> On Mon, 2005-09-19 at 19:04 +0200, Guillaume Fougnies wrote:
> > Hello,
> >
> > During the upgrade from 3.2.5 to 3.2.6, i removed my
> > compile time option SQLITE_DEFAULT_PAGE_SIZE.
> >
> >
two statements against the same database handle, they
will not be isolated. I do not understand why you would expect
that they would be.
--
D. Richard Hipp <[EMAIL PROTECTED]>
nnot debug this problem unless you provide more
information. What were you setting DEFAULT_PAGE_SIZE to,
for example. Are you sure the original database is
readable by a stock copy of 3.2.5? Can you provide
a copy of the database that does not work?
--
D. Richard Hipp <[EMAIL PROTECTED]>
xist...)
>
> The second seems to be a limitation of VS6 - it certainly isn't a
> problem in VS7. Can't really think of any neat solution around it
> either...
>
http://www.sqlite.org/cvstrac/chngview?cn=2720
--
D. Richard Hipp <[EMAIL PROTECTED]>
nts". Do you have
> any suggestions on how I can use a variable in my ORDER BY clause?
> Thanks,
> Nicole Hinderman
>
>
Changes to the ORDER BY modify the choice of algorithms used
to process the query. This requires that you rerun
sqlite3_prepare() in order to generate new c
On Sun, 2005-09-18 at 01:03 +0400, Alexander J. Kozlovsky wrote:
> Hence, SQLite deferred transactions is not serializable ones.
>
Your understanding is incorrect. SQLite does *not* release
locks in the middle of a transaction - ever. It is always
serializable.
--
D. Richard Hipp &
On Sat, 2005-09-17 at 15:13 -0500, Jolan Luff wrote:
> On Sat, Sep 17, 2005 at 03:41:21PM -0400, D. Richard Hipp wrote:
> > Version 3.2.6 is now available on the website
>
> 3.2.6 does not compile on FreeBSD and OpenBSD because they do not have
> fdatasync(). AFAICT,
rewritten.
COUNT(DISTINCT) is now supported.
The LIKE operator might use indices to speed its
search if the column being searched uses COLLATE NOCASE.
Lots of smaller bug fixes and miscellaneous
enhancements.
--
D. Richard Hipp <[EMAIL PROTECTED]>
ersions of
windows.
So to answer your question, COMMIT is much faster on Win98 because of
a bug in the operating system that can cause data loss or data
corruption
after a power failure or operating system crash.
--
D. Richard Hipp <[EMAIL PROTECTED]>
, I'm
obliged to support it forever. So I want to ponder the
issue a bit more first.
--
D. Richard Hipp <[EMAIL PROTECTED]>
.
--
D. Richard Hipp <[EMAIL PROTECTED]>
On Thu, 2005-09-15 at 13:59 +0100, Da Martian wrote:
> Hi
>
> I have 3 million rows in a table which takes up about 3.1GB on disk. The
> count(*) is slow.
>
> I have run the analyze, but apart from creating the stats table it does
> nothing.
>
> Any reason why this is? Can it be improved ?
g parse.c and no hand editing
is required.
--
D. Richard Hipp <[EMAIL PROTECTED]>
ult release. In the meantime,
you can find the patches at:
http://www.sqlite.org/cvstrac/tktview?tn=1240
--
D. Richard Hipp <[EMAIL PROTECTED]>
On Tue, 2005-09-13 at 09:08 +0200, Laurent wrote:
> I get the error :
>
>Assertion failed: xHash!=0, file hash.c, line 299
>Abnormal program termination
>
I tried the same sequence of commands and it worked
fine for me.
--
D. Richard Hipp <[EMAIL PROTECTED]>
ve to load version 3 of the TCL bindings
first, then version 2.
--
D. Richard Hipp <[EMAIL PROTECTED]>
l the optimizer without
creating any incompatibilities.
--
D. Richard Hipp <[EMAIL PROTECTED]>
On Fri, 2005-09-09 at 15:43 -0400, D. Richard Hipp wrote:
> There may be something wrong with version 3.2.5. See, for example,
> ticket #1414: http://www.sqlite.org/cvstrac/tktview?tn=1414
If you read the comments on the ticket above, you'll see that
the problem was solved by
d:
sum() == 0
sum() == NULL
sum() == the correct sum
--
D. Richard Hipp <[EMAIL PROTECTED]>
ease send me both a query and a database to
run it on, I will look into the matter and hopefully get a fix
out right away.
--
D. Richard Hipp <[EMAIL PROTECTED]>
mperature FROM antartica WHERE temperature < -150 LIMIT 1
Which gives the result you seek.
Thank you for the suggestion, though...
--
D. Richard Hipp <[EMAIL PROTECTED]>
nderstand Martin's point of view. The SQL standard
point of view makes no sense to me at all.
--
D. Richard Hipp <[EMAIL PROTECTED]>
nctions, which is what I am proposing to do
in SQLite in defiance of the SQL standard.
--
D. Richard Hipp <[EMAIL PROTECTED]>
n 0 when it has no
input.
--
D. Richard Hipp <[EMAIL PROTECTED]>
the entries are
NULL, then the answer is the sum of the non-NULL entries.
But if the number of entries is greater than zero and
they are all NULL, then the answer is NULL.
Logical, right
The more I learn about NULLs in SQL the less sense they
make...
--
D. Richard Hipp <[EMAIL PROTECTED]>
journal" files. They are used to make
sure that commits to multiple databases occurs atomically.
They should be deleted automatically. I do not know why they
are not being removed for you. I will look into it.
--
D. Richard Hipp <[EMAIL PROTECTED]>
s return NULL:
>
> SELECT AVG(b) FROM TEST;
>
AVG is implemented as SUM/COUNT. But the count is zero. So
you get a NULL.
--
D. Richard Hipp <[EMAIL PROTECTED]>
SQLite uses 64-bit signed integers (8 bytes).
--
D. Richard Hipp <[EMAIL PROTECTED]>
mes that ROWIDs are consecutive, which may or may
not be the case. (Probably it is not the case.) To get the last 10
rows, I would suggest this:
SELECT * FROM mytable ORDER BY rowid DESC limit 10;
That will work as long as the optimizer doesn't try to use an index
to satisfy terms of your WHERE clause.
--
D. Richard Hipp <[EMAIL PROTECTED]>
you really want to make sure that the transfer from
pending to main is atomic, enclose the last two statements
in a transaction.
--
D. Richard Hipp <[EMAIL PROTECTED]>
TE operation in step 2 will acquire a read-lock on the
database file which will insure that no other process modifies the file
during step 3. But it is also only a read-lock so other processes can
continue to read the database while you are copying it. Step 4 releases
the file lock.
--
D. Richard Hipp <[EMAIL PROTECTED]>
l
end up doing unless somebody can suggest a good reason not
to.
--
D. Richard Hipp <[EMAIL PROTECTED]>
Can somebody with access to Win95/98/ME please test
check-in [2656] for me to make sure it didn't break
anything?
http://www.sqlite.org/cvstrac/chngview?cn=2656
--
D. Richard Hipp <[EMAIL PROTECTED]>
ing DB handles in multiple threads is
a problem.
--
D. Richard Hipp <[EMAIL PROTECTED]>
trac/tktview?tn=1272 and
http://www.sqlite.org/cvstrac/tktview?tn=1285.
--
D. Richard Hipp <[EMAIL PROTECTED]>
t
acquires the locks immediately and would thus cause the
EBUSY error when thread2 did its BEGIN. This simplifies
recovery at the price of some concurrency.
--
D. Richard Hipp <[EMAIL PROTECTED]>
s used are now
detected sooner rather than later.
--
D. Richard Hipp <[EMAIL PROTECTED]>
the lastest version of SQLite and if circumstances
are just right, LIKE will use an index.
See http://www.sqlite.org/optoverview.html#like_opt
--
D. Richard Hipp <[EMAIL PROTECTED]>
parate handle for
each thread.
--
D. Richard Hipp <[EMAIL PROTECTED]>
On Fri, 2005-09-02 at 11:59 +0200, Michael Schoen wrote:
> (1) Multiple Insert Statements
> We need to insert around 300-500 datasets/sec constantly (24/7) with 8
> till 16 fields indexed. So far we are using mysql, not only due to the
> general dbms speed, but mainly because it has a csv impo
Thanks everybody!
All the results so far seem to be in agreement with each
other and with the current behavior of SQLite. So I think
everything is good. Thx for the help.
--
D. Richard Hipp <[EMAIL PROTECTED]>
INTO t1 SELECT * FROM t1;
SELECT a, b, sum(c) FROM t1 GROUP BY a, b ORDER BY 3;
Thanks.
--
D. Richard Hipp <[EMAIL PROTECTED]>
1|1|zzz
> 1|2|xxx
> 1|3|yyy
>
Fix is at http://www.sqlite.org/cvstrac/chngview/cn=2655.
--
D. Richard Hipp <[EMAIL PROTECTED]>
;
>
> returns 1125415140
>
> If I take that resulting value and feed it to localtime()
> in Perl, either under Windows or Linux, the resulting
> date/time value is "2005-08-30 08:19:00"
>
SQLite works in UTC (aka GMT) not in localtime.
--
D. Richard Hipp <[EMAIL PROTECTED]>
sqlite.org/cvstrac/tktview?tn=1272
http://www.sqlite.org/cvstrac/chngview?cn=2521
--
D. Richard Hipp <[EMAIL PROTECTED]>
0 && exp<=350 ){ realvalue *= 0.1; exp++; }
>
Thanks. This is the problem and it is being fixed now.
--
D. Richard Hipp <[EMAIL PROTECTED]>
und
down.
So I'm not overly worried when I see round(9.95,1) come out
with 9.9. But I am concerned about the people who are seeing
results like ":.0". I wish I could reproduce that problem.
--
D. Richard Hipp <[EMAIL PROTECTED]>
SQLite version 3.2.5 is now available on the website.
http://www.sqlite.org/
This version fixes bugs found in 3.2.3 and 3.2.4.
--
D. Richard Hipp <[EMAIL PROTECTED]>
s just do a better job of it.
--
D. Richard Hipp <[EMAIL PROTECTED]>
ually
reconstruct
the key.
The usual defense against this attack (and the one used by SQLite)
is to discard the first 1000 bytes or so of information coming out
of the PRNG. No key information leaks into later bytes of the
PRNG stream (at least as far as we know) so this secures the cypher
from attack.
--
D. Richard Hipp <[EMAIL PROTECTED]>
terface does not take advantage of the new features of sqlite
> version 3 with the integers and doubles, as it convert everything to one
> string. Are there any plans to change it?
>
What version are you looking at? The latest Tcl bindings already
do this.
--
D. Richard Hipp <[EMAIL PROTECTED]>
to be compatible with BSD make.
>
OK. The line above was in a patch someone sent in for ticket
#1292: http://www.sqlite.org/cvstrac/tktview?tn=1292.
Can someone who understands make and configure perhaps suggest a
fix for this so that it will work on OpenBSD and Mac OS-X at the
same time?
--
D. Richard Hipp <[EMAIL PROTECTED]>
u find a specific problem with the 3.2.4 Makefiles, I'll be
happy to look at it. But from what I've seen so far, this looks
like a problem in your environment, not in SQLite.
--
D. Richard Hipp <[EMAIL PROTECTED]>
iew?cn=2366
--
D. Richard Hipp <[EMAIL PROTECTED]>
is hard to imagine what might have broken...
--
D. Richard Hipp <[EMAIL PROTECTED]>
3.2.5 will be forthcoming.
But I'm going to wait a few days for other bugs to emerge
before I do the next release. I would very much appreciate
it if as many people as possible will try out version 3.2.4
over the next few days and report any problems you run
across.
--
D. Richard Hipp &l
I see the problem. I'm working on the fix now. This will
result in 3.2.5, eventually.
The bug has been in the code for 2 months. Apparently nobody
tests out of CVS. :-(
--
D. Richard Hipp <[EMAIL PROTECTED]>
);
>
It works fine when I try it. Please send me your database
if you can. Use ".dump" to convert to text, then compress
the text and send private email to [EMAIL PROTECTED]
--
D. Richard Hipp <[EMAIL PROTECTED]>
Version 3.2.3 contained a memory allocation bug which could cause
a segfault when complex WHERE clauses are parsed. The problem is
fixed in version 3.2.4 which is now available on the website.
--
D. Richard Hipp <[EMAIL PROTECTED]>
;
SQLite supports variable-length records with automatic
compaction and defragmentation. Records are subject to
being moved about on the disk after any change to nearby
records.
--
D. Richard Hipp <[EMAIL PROTECTED]>
I just ran a speed comparison between version 2.8.16 and 3.2.3.
Version 3.2.3 is faster in almost every case. See
http://www.sqlite.org/speed-2816-v-323.html
--
D. Richard Hipp <[EMAIL PROTECTED]>
a little slower to commit, but it is also safer in
the face of power failures. In spite of this handicap,
SQLite version 3 still manages to be faster than version 2
in many tests.
--
D. Richard Hipp <[EMAIL PROTECTED]>
zation
enabled to prevent data loss after a power failure. So this
is not a real high priority.
--
D. Richard Hipp <[EMAIL PROTECTED]>
d a case we have missed. Please report
it.
--
D. Richard Hipp <[EMAIL PROTECTED]>
the database that caused the assert if posssible.
Or better, provide a short SQL script that causes the assert to fail
when run from the command-line client.
We'll try to get to it...
--
D. Richard Hipp <[EMAIL PROTECTED]>
ogram that is easier to write,
easier to maintain, has fewer bugs, and just works better.
--
D. Richard Hipp <[EMAIL PROTECTED]>
On Mon, 2005-08-22 at 16:54 -0600, Dennis Cote wrote:
> select *
> from MyTable
> join (select random(*) as number) as rand
> where start_col >= rand.number
> and end_col < rand.number;
>
Very nice. Dennis Cote wins todays prize for
cleverest use (abuse?) of a join!
--
801 - 900 of 1805 matches
Mail list logo
