On Mon, 24 Sep 2007 07:13:51 -0700, Gururaja Nittur wrote:
Sqlite experts,
I am running Sqlite version 3.4.1. I ran some performance tests and
observed that sqlite sometimes consumes more CPU than normal (I am
using same dataset, all inserts and recreating new database for each
test). Tried
On 9/24/07, Kees Nuyt [EMAIL PROTECTED] wrote:
On Mon, 24 Sep 2007 07:13:51 -0700, Gururaja Nittur wrote:
Sqlite experts,
I am running Sqlite version 3.4.1. I ran some performance tests and
observed that sqlite sometimes consumes more CPU than normal (I am
using same dataset, all inserts
Kees Nuyt wrote:
On Mon, 24 Sep 2007 07:13:51 -0700, Gururaja Nittur wrote:
Sqlite experts,
I am running Sqlite version 3.4.1. I ran some performance tests and
observed that sqlite sometimes consumes more CPU than normal (I am
using same dataset, all inserts and recreating new database for
On Mon, 24 Sep 2007 10:35:51 -0700, you wrote:
Kees Nuyt wrote:
On Mon, 24 Sep 2007 07:13:51 -0700, Gururaja Nittur wrote:
Sqlite experts,
I am running Sqlite version 3.4.1. I ran some performance tests and
observed that sqlite sometimes consumes more CPU than normal (I am
using same
I am running sqlite 3.4.2 and I am trying to get the extension_functions.c
extenstion to work. I have followed the directions:
How To Build a Loadable Extension Shared Library on Linux
0. untar latest sqlite3 source code in a new directory
1. cd to the newly untarred sqlite directory
2.
On Thu, 20 Sep 2007 10:14:10 -0700 drh wrote:
Sqlite3_open_v2() and SQLITE_OPEN_READONLY and a whole bunch
of other stuff is all new to 3.5.0. Version 3.5.0 is stable.
It has lots of cool stuff. Older versions are not supported
(except for paying customers) - by which we mean that if any
On 9/24/07, Kees Nuyt [EMAIL PROTECTED] wrote:
On Mon, 24 Sep 2007 10:35:51 -0700, you wrote:
Kees Nuyt wrote:
On Mon, 24 Sep 2007 07:13:51 -0700, Gururaja Nittur wrote:
Sqlite experts,
I am running Sqlite version 3.4.1. I ran some performance tests and
observed that sqlite
This contrib extension library cannot be used directly as an sqlite
loadable module because it lacks an entry point function with the prototype:
int sqlite3_extension_init(
sqlite3 *db, /* The database connection */
char **pzErrMsg, /* Write error messages here */
