Re: [sqlite] make fails on Solaris

See if your installation has "nawk" or "gawk". Then search through Makefile.in and change the "awk" invocations to "nawk" or "gawk" (three changes). It might work then. --- H S <[EMAIL PROTECTED]> wrote: > You are right. opcodes.h is corrupted. It has 0 byte.. > > I have all other files:

Re: [sqlite] make fails on Solaris

You are right. opcodes.h is corrupted. It has 0 byte.. I have all other files: lemon exists in the build directory as well as parrse.c and parse.h Here is the messages from configure gums2-sun% ../sqlite-3.2.2/configure --prefix=/dssweb/sqlite checking build system type...

Re: [sqlite] make fails on Solaris

> Hi, > > Could someone please shed some light what I should do? > I've got the following errors. > > Thank you, > Isarin > > gums-sun% make > ./libtool --mode=compile gcc -g -O2 -DOS_UNIX=1 -DHAVE_USLEEP=1 -I. > -I../sqlite-3.2.2/src -DNDEBUG -DSQLITE_OM\ > IT_CURSOR -c

[sqlite] make fails on Solaris

Hi, Could someone please shed some light what I should do? I've got the following errors. Thank you, Isarin gums-sun% make ./libtool --mode=compile gcc -g -O2 -DOS_UNIX=1 -DHAVE_USLEEP=1 -I. -I../sqlite-3.2.2/src -DNDEBUG -DSQLITE_OM\ IT_CURSOR -c ../sqlite-3.2.2/src/alter.c mkdir .libs

[sqlite] SQLITE3 database open from multiple processes

Hi, Is it safe to have the database open by two separate processes? I have an application that uses the database somewhat often and runs 24/7. I have another application that runs once / day. The second application inserts some data into a table that is not coming up in the database. I have

[sqlite] Newbie Help Please

Heyas, I tried to do the quick-start example and I could not get it to work. It is not explicit enough for some like me. First off, the quickstart doesn't specify that you need to include the source (just the external interface header). But since it does not come with a *.lib I tried to

Re: [sqlite] Multi-threading.

On Fri, Jul 15, 2005 at 01:04:50PM -0400, Paul G wrote: > the issue wasn't necessarily the thread implementation per se, but the fact > that threads were treated as processes for scheduling purposes and hence > scheduled with the regular process scheduler, which was not efficient for a > large

Re: [sqlite] Multi-threading.

D. Richard Hipp wrote: On Fri, 2005-07-15 at 16:41 +0530, Roushan Ali wrote: Hello all, Can we use single sqlite_open handle(global) across threads( if all database operations are serialized by using semaphore) ? Please help. Opening a database connection in one thread

Re: [sqlite] Multi-threading.

Andrew Piskorski wrote: On Fri, Jul 15, 2005 at 04:21:05PM +0300, Cariotoglou Mike wrote: memory and cpu-wise. on Linux, this is nothing, it can handle it easily. otoh, 500 threads for windows is business as usual, but threading on Linux, is , I hear, iffy at best. Linux runs

Re: [sqlite] Multi-threading.

- Original Message - From: "Andrew Piskorski" <[EMAIL PROTECTED]> To: Sent: Friday, July 15, 2005 1:05 PM Subject: Re: [sqlite] Multi-threading. > On Fri, Jul 15, 2005 at 04:21:05PM +0300, Cariotoglou Mike wrote: > > > memory and cpu-wise. on Linux, this is

Re: [sqlite] Multi-threading.

D. Richard Hipp wrote: Actually, this seems like a good opportunity to repeat my oft-ignored advice to not use more than one thread in a single address space. If you need multiple threads, create multiple processes. I think its not really an acceptable option for those who are on Windows

Re: [sqlite] Multi-threading.

Roushan Ali wrote: Hi, Thanks for your response. I don't have any idea how multiple connection objects work. Can you please tell us something about that. I wrappered the C interface to SQLite3 via a C++ Class called "CSqlite3". The constructor does NOT open the database, it just

Re: [sqlite] Multi-threading.

Hi, Thanks for your response. I don't have any idea how multiple connection objects work. Can you please tell us something about that. Thanks, Roushan On Fri, 2005-07-15 at 20:15, Dennis Jenkins wrote: > Roushan Ali wrote: > > >Thanks Richard for your reply. > > > >Actually, we have written

Re: [sqlite] Multi-threading.

On Fri, Jul 15, 2005 at 08:27:14AM -0400, D. Richard Hipp wrote: > [...] > I am constantly amazed at the prevailing idea (exemplified > by Java) that software should be strongly typed and should > not use goto statement or pointers - all in the name of > reducing bugs - but that it is OK to use

Re: [sqlite] Multi-threading.

Roushan Ali wrote: Thanks Richard for your reply. Actually, we have written a windows application which uses four threads. Each thread may have to add/delete thousands of entries in the database( for performance reason , we don't want to open/close the database for each insertion/deletion)

Re: [sqlite] Multi-threading.

Thanks Richard for your reply. Actually, we have written a windows application which uses four threads. Each thread may have to add/delete thousands of entries in the database( for performance reason , we don't want to open/close the database for each insertion/deletion) .If we use different

Re: [sqlite] How to delete all rows in table (TRUNCATE) without creating journal file(s)?

> Disabling the journal would roughly half the amount > of disk (flash) I/O required. If it currently takes > 2 minutes to delete, disabling the journal would > reduce that to about 1 minutes. Still a long time. You were aware that flash memory has a limited number of write cycles before it

[sqlite] NOCASE COLLATION + INDEX - Any known issue?

Hi, I have ported Sqlite 3.0.8 source onto Arm platform and it is having some problems when I create INDICES for the columns that have COLLATE NOCASE conditions. Is there any known issue and if so any fixes already for such a problem? I find that when I insert into the table with one of its

RE: [sqlite] Multi-threading.

which gives me the opportunity to repear my oft-ignored reply :) what you say is true, provided the OS is geared towards multiple processes. which is not true for windows, but is true for *ix, as400 and other environments. if you need, say, a server that handles 500 sessions, and attempt to do

[sqlite] sqlite3_errmsg

Have I to free the string buffer returned by sqlite3_errmsg? If I write something like: char *err; err = (char *) sqlite3_errmsg(db); if (err) sqlite3_free(err); or if (err) free(err); then, OSX gives me a "Deallocation of a pointer not malloced" error... So it seems that I haven't to free it,

Re: [sqlite] Multi-threading.

On Fri, 2005-07-15 at 16:41 +0530, Roushan Ali wrote: > Hello all, > Can we use single sqlite_open handle(global) across threads( > if all database operations are serialized by using semaphore) ? Please > help. > Opening a database connection in one thread and using it in

[sqlite] Multi-threading.

Hello all, Can we use single sqlite_open handle(global) across threads( if all database operations are serialized by using semaphore) ? Please help. Regards, Roushan