I found the following for "lemon" in the sqlite-3.3.6 distribution :
===
> lemon -x
Lemon version 1.0
> lemon /dev/null
Segmentation fault
> gdb ./lemon
GNU gdb 6.4
Copyright 2005 Free Software Foundation, Inc.
GDB is free sof
There seems to be a bug in the memoryTruncate function in the pager. When it
iterates through the pages I saw that there were page numbers of 0 where no
action was being taken. As the number of deletes increased, the number of
page number 0s increased. By making the following modification I no lon
Mikey C <[EMAIL PROTECTED]> wrote:
> One of my databases reports the following error, although in practice the
> database seems fine:
>
> *** in database main ***
> Page 101 is never used
>
> Any ideas/suggestions? Is this something to worry about? Can it be
> "fixed"?
>
VACUUM should clear t
One of my databases reports the following error, although in practice the
database seems fine:
*** in database main ***
Page 101 is never used
Any ideas/suggestions? Is this something to worry about? Can it be
"fixed"?
Cheers,
Mike
--
View this message in context:
http://www.nabble.com/inte
>
>
> >gcc -g -O2 -DOS_BEOS=1 -DSQLITE_DISABLE_LFS -DHAVE_USLEEP=1 -I. -I./src
> -DNDEBUG -DTHREADSAFE=1 -DSQLITE_THREAD_OVERRIDE_LOCK=-1
> -DSQLITE_OMIT_CURSOR
> > -DHAVE_READLINE=0 -o sqlite3 ./src/shell.c ./.libs/libsqlite3.a
> -lroot -lbe -lreadline $ sqlite3 test.db SQLite version 3.3.5 Ent
Hi Christian,
We're using a derivative of os_unix.c from the 3.3.5 source package; the checks
are in the code to look for the SQLITE_DISABLE_LFS flag; as you can see, it's
being set duing the build process. Yet the resulting code somehow seems to be
looking for LFS.
BeOS does have a POSIX-lik
On Fri, 9 Jun 2006, Pat Wibbeler wrote:
I'm curious - how does this avoid the buggy NFS fcntl() problem
mentioned under FAQ 7?
http://www.sqlite.org/faq.html
Does it use an external locking mechanism?
sortof. basically rq setups a directory like this
q/db
q/lock
q/...
here the 'lock
"Lists Hammersley" <[EMAIL PROTECTED]> wrote:
> On 6/9/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > If you want to preserve the traditional File/Open + File/Save
> > semantics, you could create an in-memory SQLite database then
> > copy the disk database to the in-memory database on File/Op
On 6/9/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
If you want to preserve the traditional File/Open + File/Save
semantics, you could create an in-memory SQLite database then
copy the disk database to the in-memory database on File/Open,
and copy the other way on File/Save.
Doesn't this re
"Lists Hammersley" <[EMAIL PROTECTED]> wrote:
>
> We have an existing application which stores data out to flat files.
> We would like to use SQLite as the storage mechanism for column-like
> data, other datatypes would remain in flat-files. However, there are a
> few use cases which make it diff
On 6/9/06, Christian Smith <[EMAIL PROTECTED]> wrote:
On Thu, 8 Jun 2006, [EMAIL PROTECTED] wrote:
> I also occasionally back up the database using subversion ("svn
> commit"), while the app that uses it is still running. My belief is
> that subversion only reads a file to commit it, and doesn'
Hi,
Could anyone advise on best practices for using SQLite as storage when
used in an existing application which uses file-based project storage?
We have an existing application which stores data out to flat files.
We would like to use SQLite as the storage mechanism for column-like
data, other
Mikey C <[EMAIL PROTECTED]> wrote:
>
> drh, are you interested in putting this code on your website?
>
You are more than welcomed to put the code in the contributed
code section of the website:
http://www.sqlite.org/contrib
As for folding the changes into the source tree, that depends
a lot
On Thu, 8 Jun 2006, Doug Shelton wrote:
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
On Thu, 8 Jun 2006, [EMAIL PROTECTED] wrote:
I also occasionally back up the database using subversion ("svn
commit"), while the app that uses it is still running. My belief is
that subversion only reads a file to commit it, and doesn't write to it,
but it's possible that is wrong.
Subvers
>gcc -g -O2 -DOS_BEOS=1 -DSQLITE_DISABLE_LFS -DHAVE_USLEEP=1 -I. -I./src
-DNDEBUG -DTHREADSAFE=1 -DSQLITE_THREAD_OVERRIDE_LOCK=-1
-DSQLITE_OMIT_CURSOR
> -DHAVE_READLINE=0 -o sqlite3 ./src/shell.c ./.libs/libsqlite3.a
-lroot -lbe -lreadline $ sqlite3 test.db SQLite version 3.3.5 Enter
".help" for
Cool,
I all ready have the code for a library of functions working with SQLite
V3.3.5 source.
This has been integrated into the SQLite code at compile time using
conditional compilation.
Math functions:
acos
asin
atan
atn2
atan2
acosh
asinh
atanh
degrees
radians
cos
sin
tan
cot
cosh
sinh
tanh
17 matches
Mail list logo