Re: [sqlite] sqlite 3.0.0 build issues

2004-06-21 Thread D. Richard Hipp
Doug Currie wrote:
The TEMP_STORE features should have been fully implemented by
check-in [1302] on 2004-Apr-23.  Have you observed otherwise?

1. Searching for TEMP_STORE in the sources, I see it described in the
comments in main.c but it does not appear to be used anywhere in the
code. So, this compiler macro does nothing as far as I can tell.
2. There is support for pragma temp_store -- but even this doesn't
seem to have any affect on operation... searching the sources I can't
find any use of db->temp_store (perhaps I am not following the logic).
Yep.  Looks like it got unimplemented again with check-in [1325]
on 2004-May-08.
--
D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: [sqlite] sqlite 3.0.0 build issues

2004-06-21 Thread D. Richard Hipp
Doug Currie wrote:
> I have not modified the sqlite sources to implement the TEMP_STORE features.
>
The TEMP_STORE features should have been fully implemented by
check-in [1302] on 2004-Apr-23.  Have you observed otherwise?
--
D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: [sqlite] sqlite 3.0.0 build issues

2004-06-21 Thread Doug Currie
Replying to my own message...

I bit the bullet and installed autoconf under msys/mingw. Using this
tool I updated configure.ac and Makefile.in to address some of the
build issues identified below -- everything but the OMIT macros. Of
course, I have not modified the sqlite sources to implement the
TEMP_STORE features.

The configure file ends up with a few unrelated changes (hey, it's
autoconf, what would you expect?) but they look minor. If this causes
anyone problems, I apologize in advance. Please let me know if you
think I have broken something you depend upon.

The new options are called
  --enable-threadsafe  Support threadsafe operation
  --enable-tempstore   Use an in-ram database for temporary tables 
(never,no,yes,always)

E.g.,

../sqlite/configure --enable-tempstore=no --enable-threadsafe

e

Sunday, June 20, 2004, 12:36:56 AM, I wrote:

> There are several build options in the configure/make of sqlite3 that
> are obsolete, and others that are missing.

> ENCODING is obsolete since it is specified in the open calls now.
> There are still several references to it, though, in the make and
> autoconf files, and these should all be removed.

> INMEMORYDB and SQLITE_OMIT_INMEMORYDB are obsolete since the red-black
> tree implementation is now gone. Again, references to these should be
> removed from the make and autoconf files.

> INCOREFLAGS and in particular TEMP_STORE are in limbo. The values are
> set but never used. E.g., INCOREFLAGS is set in Makefile but never
> used there. TEMP_STORE is initialized in sqliteInt.h and documented in
> several comments, but is never used in the code.

> I suspect that the intention is that sqlite3BtreeFactory use
> TEMP_STORE in certain circumstances, but presently it uses neither
> TEMP_STORE nor the db->temp_store set by pragma. In fact, even the
> flag BTREE_MEMORY which is set by sqlite3BtreeFactory when the
> filename is empty is ignored by sqlite3BtreeOpen.

> The THREADSAFE macro is used in all three os_xxx.c files, but is not
> supported by the autoconf files (configure.ac and Makefile.in). It
> would be really nice to add this when configure.ac is updated next.

> It would also be nice to change configure.ac so that only one of
> -DOS_WIN=1 or -DOS_UNIX=1 is specified in TARGET_CFLAGS. Only one is
> necessary (the other will be set in os.h) and it would make the
> console dribble from make much easier to read.

> There are several SQLITE_OMIT_ macros that should also be supported by
> the autoconf files.

> Disclaimer: I don't use autoconf, but I'd be willing to help with the
> source updates if somebody familiar with autoconf was willing to do
> the configure (+ aclocal.m4 etc.) file generation and linux testing.

> e



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[sqlite] sqlite 3.0.0 build issues

2004-06-19 Thread Doug Currie
There are several build options in the configure/make of sqlite3 that
are obsolete, and others that are missing.

ENCODING is obsolete since it is specified in the open calls now.
There are still several references to it, though, in the make and
autoconf files, and these should all be removed.

INMEMORYDB and SQLITE_OMIT_INMEMORYDB are obsolete since the red-black
tree implementation is now gone. Again, references to these should be
removed from the make and autoconf files.

INCOREFLAGS and in particular TEMP_STORE are in limbo. The values are
set but never used. E.g., INCOREFLAGS is set in Makefile but never
used there. TEMP_STORE is initialized in sqliteInt.h and documented in
several comments, but is never used in the code.

I suspect that the intention is that sqlite3BtreeFactory use
TEMP_STORE in certain circumstances, but presently it uses neither
TEMP_STORE nor the db->temp_store set by pragma. In fact, even the
flag BTREE_MEMORY which is set by sqlite3BtreeFactory when the
filename is empty is ignored by sqlite3BtreeOpen.

The THREADSAFE macro is used in all three os_xxx.c files, but is not
supported by the autoconf files (configure.ac and Makefile.in). It
would be really nice to add this when configure.ac is updated next.

It would also be nice to change configure.ac so that only one of
-DOS_WIN=1 or -DOS_UNIX=1 is specified in TARGET_CFLAGS. Only one is
necessary (the other will be set in os.h) and it would make the
console dribble from make much easier to read.

There are several SQLITE_OMIT_ macros that should also be supported by
the autoconf files.

Disclaimer: I don't use autoconf, but I'd be willing to help with the
source updates if somebody familiar with autoconf was willing to do
the configure (+ aclocal.m4 etc.) file generation and linux testing.

e



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]