Re: [sqlite] count(*) - maybe a 3rd

Hi, If a table has a primary key selecting count(*) using it maybe faster if there is a difference of the number of rows stored per page. A wide table will do more io than the index. The table names is not very wide but does consume more disk space than than the primary keys index. sql3>

Re: [sqlite] timer in shell.c

Hi Brannon, Try this: SQLite version 3.3.6 Enter ".help" for instructions sql3> .help .databases List names and files of attached databases .dump ?TABLE? ... Dump the database in an SQL text format .echo ON|OFF Turn command echo on or off .exit Exit

Re: [sqlite] problems compiling with arm-linux-gcc

Maybe this" char errMsg; -> char *errMsg --- Keiichi McGuire <[EMAIL PROTECTED]> wrote: > Hi John, > I still get an error when i use the -lsqlite switch. > When i take that out it > says: > incompatible types in assignment > passing arg 3 of 'sqlite_open' from incompatible > pointer type > >

Re: [sqlite] id INTEGER PRIMARY KEY vs PRIMARY KEY (id) ???

yup --- John Stanton <[EMAIL PROTECTED]> wrote: > A simple program which uses the API will give you > the defined type and > the actual storage format selected by Sqlite. That > would leave you in > no doubt. > > RohitPatel wrote: > > Hi SQLite users, > > > > In SQLite3 (3.3.4), > > >

Re: [sqlite] Re: attached databases

Thanks Igor! --- Igor Tandetnik <[EMAIL PROTECTED]> wrote: > carl clemens > > wrote: > > Is there away to get sqlite3 *db pointer to an > > attached database? I'm looking to load user > defined > > functions into them from a shared library. >

[sqlite] attached databases

Hi Users, Is there away to get sqlite3 *db pointer to an attached database? I'm looking to load user defined functions into them from a shared library. Does this make sense or is there a better way? Thanks in advance. Carl __ Do You Yahoo!?

Re: [sqlite] in-memory database and threads

Why sure Carly, no problem. ../bin/memdb create tables: 0.001289 load data: 0.046146 create indexes: 0.037478 Thread[0] 0.000319 Key[103407575] Date[20050107160130] Amount [64.94] Thread[0] 0.63 Key[103411009] Date[20050107200150] Amount [740.52] Thread[0] 0.52

[sqlite] in-memory database and threads

Hello sqlite-users, If using an in-memory database, do the possible db corruption problems when using multiple threads go away and can the same db handle returned from the sqlite3_open call in the main thread be used by the worker threads? If not would it help to use mutexes to syncronize

[sqlite] in-memory database and threads

Hello sqlite-users, If using an in-memory database, do the possible db corruption problems when using multiple threads go away and can the same db handle returned from the sqlite3_open call in the main thread be used by the worker threads? If not would it help to use mutexes to syncronize

[sqlite] in memory database threads

Hello sqlite-users, If using an in-memory database, do the possible db corruption problems when using multiple threads go away and can the same db handle returned from a sqlite3_open call in the main thread to the worker threads? If not would it help to use mutexes to syncronize access to the db