NAME
rq v2.3.3
SYNOPSIS
rq (queue | export RQ_Q=q) mode [mode_args]* [options]*
URIS
http://codeforpeople.com/lib/ruby/rq/
http://raa.ruby-lang.org/project/rq/
http://www.linuxjournal.com/article/7922
DESCRIPTION
ruby queue (rq) is a zero-admin zero-configuration tool used to
How does one disable large file support? As mentioned in comments, I've added
-DSQLITE_DISABLE_LFS to the Makefile, but continue to get errors indicating
lack of kernel support for large files. The following lines are the end of my
compile (so you can see make options) and the behavior of the
[EMAIL PROTECTED] wrote:
> Dennis Jenkins <[EMAIL PROTECTED]> wrote:
>
>> I would like to know where the best place in sqlite is to patch to
>> have it record (syslog for unix, OutputDebugString() for windows,
>> nothing fancy) each time it decides to use an index to satisfy a query.
>>
Dennis Jenkins <[EMAIL PROTECTED]> wrote:
>
> I would like to know where the best place in sqlite is to patch to
> have it record (syslog for unix, OutputDebugString() for windows,
> nothing fancy) each time it decides to use an index to satisfy a query.
The index decisions are all made in
Hello all,
I would like to know where the best place in sqlite is to patch to
have it record (syslog for unix, OutputDebugString() for windows,
nothing fancy) each time it decides to use an index to satisfy a query.
For that matter, also each time is runs a select query and decided to
not
On 6/8/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
On Jun 08, 2006, at 18:20 UTC, [EMAIL PROTECTED] wrote:
> See section 6.0 at http://www.sqlite.org/lockingv3.html
Thanks. Nothing there obviously applies in this case -- there was no power
failure, and no files were moved or deleted as
On Jun 08, 2006, at 18:20 UTC, [EMAIL PROTECTED] wrote:
> See section 6.0 at http://www.sqlite.org/lockingv3.html
Thanks. Nothing there obviously applies in this case -- there was no power
failure, and no files were moved or deleted as far as I'm aware -- but these
are good tips to keep in
Michael Scharf wrote:
Without journalling, you cannot have a ROLLBACK command.
And the semantics of UPDATE become UPDATE OR FAIL instead
of the default UPDATE OR ABORT. The difference is subtle,
but important.
There are other reasons to disable the rollback journal:
Suppose you want to
"Joseph J. Strout" <[EMAIL PROTECTED]> wrote:
>
> So clearly my database is corrupted. My two questions (three
> questions!) are, how can this happen?
See section 6.0 at http://www.sqlite.org/lockingv3.html
> Is there any way to prevent it?
Don't do the things described in the document
I've been using a SQLite database for a few weeks. Today, it
suddenly stopped working. The database has a single table, and can
correctly report that:
select name, sql from sqlite_master
|name |sql
I've been using a SQLite database for a few weeks. Today, it
suddenly stopped working. The database has a single table, and can
correctly report that:
select name, sql from sqlite_master
|name |sql
> 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.
> So if a statement acquires a lock on the database file in one
> thread and you try to finalize the
On Thu, 2006-06-08 at 03:58 +0200, Michael Sizaki wrote:
> Hi Mark,
>
> have you tried to do a VACUUM on the database?
> It helps a lot when it comes to the 'read ahead'
> feature of the database.
>
> Michael
Michael,
Well, I just repeated my tests to see if vacuum would have any
noticeable
Hi,
I use sqlite3.3.4 on windows.
I have two instances of a program that attempt to simultaneously write to
the same database.db file. When I run them together, I observe that a
database.db-journal file is created. The programs crash with an exception
thrown. The exception found in the
Michael Somos <[EMAIL PROTECTED]> wrote:
> I just ran across this little bug
>
>
> > sqlite3
> SQLite version 3.3.6
> Enter ".help" for instructions
> sqlite> .import x y
> Segmentation fault
>
>
Thanks
Mikey C <[EMAIL PROTECTED]> wrote:
>
> I am in need of some new SQL functions and wanted to ask advice on the best
> way to integrate these functions into SQLite 3.
>
See http://www.sqlite.org/cvstrac/wiki?p=LoadableExtensions
This is still a work in progress...
--
D. Richard Hipp <[EMAIL
I just ran across this little bug
> sqlite3
SQLite version 3.3.6
Enter ".help" for instructions
sqlite> .import x y
Segmentation fault
gdb shows where it took place :
No problem. In fact, I had to consult the docs again to be sure! I've
sorted through these several times myself.
They are quite good, though I have to admit that I'm constantly having
to consult them to remember how the locking works. I do agree that a
BEGIN SHARED would be nice for cases
On Wed, 2006-06-07 at 00:03 -0500, David Wollmann wrote:
> Mark Drago wrote:
> > Hello,
> >
> > I'm writing a web cache and I want to use SQLite to store the log of all
> > of the accesses made through the web cache. The idea is to install this
> > web cache in large institutions (1000-5000
Hello,
Regardless of program loading design,
wouldn't this feature be better coded
using function pointers? Ie. Have a
"register/load" function that maps
functions in the exe?
PS. It would be helpful to have
sqlite3OSMalloc() and sqlite3OSFree()
as function pointers as well, so an
application
Андрей Лапин wrote:
Hi.
In mine to a database after the size of a file of base has reached
4096 Mb, I am not added any more records. After a command sqlite3_step
the mistake (sqlite3_errmsg) stands out: "SQL logic error or missing
database".
Please help, it is necessary for me to process a lot
"Kervin L. Pierre" <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I was under the impress that we could never
> get an SQLITE_BUSY, not even on COMMIT if
> we use BEGIN EXCLUSIVE. But this seems to
> say that COMMITs on exclusive transactions
> can through SQLITE_BUSY?...
>
You can get an SQLITE_BUSY
Hello,
I was under the impress that we could never
get an SQLITE_BUSY, not even on COMMIT if
we use BEGIN EXCLUSIVE. But this seems to
say that COMMITs on exclusive transactions
can through SQLITE_BUSY?...
--- [EMAIL PROTECTED] wrote:
> then start the transaction initially with BEGIN
>
How does introducing a new shared library format that supports
automatic bidirectional linking (as in Unix) break backwards
compatibility? Nobody says they have to stop supporting DLLs.
Just provide something better in addition to DLLs...
Despite disliking many of the Win32 "features", I see
24 matches
Mail list logo
