Re: [sqlite] Compiler errors

se files belong to a normal sqlite build. So these symbols should be defined if you link your program correctly with the sqlite library... - Danny -- Danny Reinhold Reinhold Software & Services - To unsubscribe, e-mail: [EM

Re: [sqlite] Compiling a shared library (.so) WITH threadsafe option enabled

Hi again, > Actually, the -DNDEBUG=1 is not SQLite specific. This is how > you disable assert()s. The SQLite library is full of assert()s > for sanity checking. But it is smaller and runs twice as fast > if you leave them out. Oh yes, you are right. (I forgot it because I don't use assert()

Re: [sqlite] Compiling a shared library (.so) WITH threadsafe option enabled

a SQLite specific directive while -g is a compiler option for the gcc... - Danny -- Danny Reinhold Reinhold Software & Services - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: [sqlite] Compiling a shared library (.so) WITH threadsafe option enabled

ecutables and libraries while -DNDEBUG=1 causes the compiler to not generate them (and so it's useless to strip the library after creation)... - Danny -- Danny Reinhold Reinhold Software & Services http://www.rsas.de - To u

Re: [sqlite] Developers of SQLite

rchive)... BTW: I found it in a thread about autoconf, automake and friends. What happened to this? Is somebody actively maintaining these build method for SQLite? - Danny -- Danny Reinhold Reinhold Software & Services - To u

Re: [sqlite] Where statements are they case sensitive?

bug on this or was it by design?? I think it is very well designed and should not be changed. If you want case insensitive where clauses, use something like this: select * from sqlite_master where upper(name) = 'MYTABLE'; - Danny -- D

Re: [sqlite] Checking the busy state

ent library would be API compatible to the SQLite library itself. Then you could turn a simple SQLite application to a client application for your SQLite server simply by linking against your client library instead of linking with SQLite directly... Just an idea... - Danny -- Danny Reinhold Rein

Re: [sqlite] Performance benchmarking

> Danny Reinhold wrote: > > DRH tested inserts with and without transactions on several > > DBMSs. PostgreSQL and MySQL where faster _without_ > > explicit transactions. > > That looks a bit strange to me... > If you are referring to Test 1 and Test 2 at http://www.s