Hello List,
Got this email from this a developer of XMMS2 Sounds a bit scary,
anyone have seen this before?
-- Tobias
Begin forwarded message:
From: Alexander Botero-Lowry <[EMAIL PROTECTED]>
Date: måndag 3 jul 2006 16.13.29 GMT-04:00
To: [EMAIL PROTECTED]
Subject: Fw:
I've not had any problems with sqlite3_busy_timeout on Linux.
And I do not have NetBSD handy for testing. Not sure what the
problem might be.
Hello,
Anything we can do to help? Give you access to a NetBSD machine, put
in some debug somewhere?
-- Tobias
Kiel W. wrote:
Ian Monroe wrote:
I do not see how such a major change can be justified in a minor point
release. For instance, currently amaroK does not work when using a
sqlite database on Debian Sid since they package it with sqlite 3.2.5.
Just my two cents, but if this change is breaking
El 02-03-2006, a las 13:35, [EMAIL PROTECTED] escribió:
The VACUUM command does something very much like this:
sqlite3 olddb .dump | sqlite3 newdb; mv newdb olddb
I say "much like" the above because there are some
important differences. The VACUUM command transfers
the data from the old
Hello,
I guess this subject is a bit worn out. But I am having scalabillity
problems with SQLite in XMMS2. We have dimensioned XMMS2 to handle
insanely huge media libraries, playlists and clients. Our goal is to
be able to run medialibs with 50.000 files without problem. Our
backend is
El 24-03-2006, a las 16:08, [EMAIL PROTECTED] escribió:
Elcin Recebli <[EMAIL PROTECTED]> wrote:
Hi.
You're joining the table with itself using 'id'. However, there's
no index just on that field. I'm not sure how exactly SQLite
utilises indices, but it might be unable to use index on
I downloaded your database and the query above was indeed slow.
But then I ran "ANALYZE" so that SQLite can gather statistics
on the various indices, then reran the query. This time, SQLite
was able to use the ANALYZE results to make better index choices
and the query is quite speedy.
The
Hello,
We (XMMS2 Team) have been using SQLite for quite some time now, it's
used to cache metainformation about songs played. It can also be used
to be searched and store addtional information. SQLite fits us very
well and have been a good complement to xmms2.
My primary platform is MacOSX and
Thanks for your reply,
D. Richard Hipp wrote:
On Fri, 2005-04-22 at 09:10 +0200, Tobias RundstrÃm wrote:
First of all performance is TERRIBLE, without syncronous=off I see
insert times of up to 1 second for one row?!
This is the F_FULLFSYNC issue. It's a sad hardware story and there is
nothing
Pierre D. wrote:
Hi
I'm currently developing a package manager (for linux) (yes I know, yet
another, useless...) and I'm using XML files for the database. But the
problem of that way is the slowdown and the memory cost of xml files + XPath
query
So I'm exploring other ways to store the
[EMAIL PROTECTED] wrote:
Le Samedi 23 Avril 2005 14:34, Tobias Rundström a écrit :
select p.name from packages p join files f on f.pkgid = p.pkgid where
f.filename="/usr/bin/gcc";
It is as slow as the previous query :(
Poor indexes? make sure that you have a index on pkgid in both table
11 matches
Mail list logo
