the url returns
"
Currently, the playback feature of Google Video isn't available in your
country.
We hope to make this feature available more widely in the future, and we
really appreciate your patience.
"
On 6/4/06, A. Pagaltzis <[EMAIL PROTECTED]> wrote:
Hi,
for those who haven't
Hi,
for those who haven’t noticed, a video of a 45-min talk by
Dr. Hipp about SQLite that he gave at Google has been posted on
Google Video:
http://video.google.com/videoplay?docid=-5160435487953918649
Not much nitty-gritty, but a nice 20,000 ft view; there isn’t
much news to me in it, but
Hello John,
Thank you for your answer but I suspect this is not the reason for the
following cases:
1. I modified the code to check for the sqlite3_close return value and it
never fails; the error keeps happening though
2. If I remove completely the sqlite3_close statement, the error still
occurs
Joe Wilson wrote:
Remember, that the operating system bug that is causing all the
multithreading grief is that file locks created by one thread
cannot be reliably removed or modified by a different thread.
You could have a single thread that exclusively performs file locking/unlocking.
This
You don't test for an error on your close statement. I suspect that the
Sqlite databases are not being closed because activity is not finalized.
Your error pops up when you have a very large number of databases open.
JS
Costas Stergiou wrote:
Hello everyone,
I lately came upon a very
yuyen wrote:
> Ok, finally I found the problem is that the PHP and Apache are installed
> in local drive and I put the sqlite database file on a remote file
> server which is a Linux / Samba. I can use sqlite3.exe to open that
> remote database with a mapped remote drive. And Insert, Update and
>
> Remember, that the operating system bug that is causing all the
> multithreading grief is that file locks created by one thread
> cannot be reliably removed or modified by a different thread.
You could have a single thread that exclusively performs file locking/unlocking.
This thread would wait
If you test against 3.2.1, just use your original where clause
and original index pk_data:
where utime >= 1146441600 and utime < 114912
as I don't know what effect the unary +'s would have on it.
--- Joe Wilson <[EMAIL PROTECTED]> wrote:
> For my databases, GROUP BY is slower in recent
For my databases, GROUP BY is slower in recent SQLite releases
because my queries are not able to use indexed columns for
GROUP BY items by design:
http://www.mail-archive.com/sqlite-users%40sqlite.org/msg15563.html
I'm curious what sort of timings you'd get with SQLite 3.2.1.
Hello everyone,
I lately came upon a very strange error that occurs at random times. I
managed to trace down and produce a small piece of code to reproduce it.
I am using Delphi and the sqlite3.dll (latest) but I am sure that this error
is not related to something other than the engine. Here is
yuyen wrote:
> Ok, finally I found the problem is that the PHP and Apache are
> installed in local drive and I put the sqlite database file on a
> remote file server which is a Linux / Samba. I can use sqlite3.exe to
> open that remote database with a mapped remote drive. And Insert,
> Update and
11 matches
Mail list logo
