> On Dec 19, 2019, at 4:49 PM, Mike Bentley wrote:
>
> Is it true that "Each index name must be unique in the database"?
Yes. You're right that the docs don't seem to spell this out, but since the
syntax to delete an index is "DROP INDEX ", you couldn't have
multiple indexes with the same
Puneet Kishor wrote:
To Richard --
So in my test, SQLite is a little faster. Perhaps the difference
might be in a bad implementation of the SQLite bindings for Perl,
or perhaps the "mysql" command-line shell is less than optimal.
You perhaps meant "PHP" instead of "Perl" as that is what hannes
Hannes Roth wrote:
Hi.
I don't want to publish that table I used to make that benchmark. So I
created some random data:
http://dl.magiccards.info/speedtest.tar.bz2
$db = sqlite_open("speedtest.sqlite");
$result = sqlite_query($db, "SELECT * FROM speedtest WHERE text5 LIKE
'%a%'");
rich coco wrote:
i am curious as to the discrepancies in 'sys' time between
sQLite and mySQL (9.12s .vs 1.96s as reported below).
SQLite lacks a persistent server, so it has to flush its
cache and reread every page of the database for each of
the 100 queries. This takes time. MySQL, on the other
AIL PROTECTED]
Sent: Wednesday, April 14, 2004 1:39 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [sqlite] MySQL / SQLite
At 19:32 2004-04-14, you wrote:
>>Yes, but are mysql_query and sqlite_query really doing the same thing? It
>>is quite possible that mysql_query does
At 19:32 2004-04-14, you wrote:
Yes, but are mysql_query and sqlite_query really doing the same thing? It
is quite possible that mysql_query doesn't actually perform the complete
query, while sqlite_query does. I think a better test would be to do the
query and then step through all of the
Hannes Roth wrote:
I don't want to publish that table I used to make that benchmark. So I
created some random data:
http://dl.magiccards.info/speedtest.tar.bz2
$db = sqlite_open("speedtest.sqlite");
$result = sqlite_query($db, "SELECT * FROM speedtest WHERE text5 LIKE
'%a%'");
Hannes Roth wrote:
$db = sqlite_open("speedtest.sqlite");
$result = sqlite_query($db, "SELECT * FROM speedtest WHERE text5 LIKE
'%a%'");
include("MySQL.php");
$erg = mysql_query("SELECT * FROM speedtest WHERE text5 LIKE '%a%'");
MySQL: 0.13727307319641
SQLite: 0.17734694480896
Yes, but are
Hannes Roth wrote:
Ok:
-18 fields, all strings or numbers.
-No indices.
-The query I used is "SELECT * FROM table WHERE field1 LIKE '%foo%'.
This is similar to Test-5 at http://www.sqlite.org/speed.html
In Test-5, SQLite is 30% faster than MySQL. I do not know
what the difference might be from
PROTECTED]
Subject: Re: [sqlite] MySQL / SQLite
Hannes Roth wrote:
> 2. Why is SQLite twice as fast when using a small database (<3000 rows)
> and twice as slow when using a large database (>8000 rows)?
>
The speed comparison at http://www.sqlite.org/speed.html uses tables
with
Hannes Roth wrote:
2. Why is SQLite twice as fast when using a small database (<3000 rows)
and twice as slow when using a large database (>8000 rows)?
The speed comparison at http://www.sqlite.org/speed.html uses tables
with 25000 rows and is twice as fast as MySQL. I don't know why yours
is
Hannes Roth schrieb:
1. Why is the SQLite database much much bigger than the MySQL table and
the raw csv file? I didn't use any index and vacuumed all the time ;)
SQLite does store everything as string, therefore the DB cannot be
significantly small than the CVS-file. MySQL does store
12 matches
Mail list logo
