Re: [sqlite] --prefix

On Tue, 2007-05-29 at 13:11 -0700, Smith1, Robert E wrote: > Hi, > > I am trying to install sqlite3 on Sun Solaris 2.8. I am not root so I > cannot install to /usr/local. I start configure with > --prefix=/ptmp/usr/localto try to get it to install to a different > directory. But I get the

Re: [sqlite] --prefix

[In the message "[sqlite] --prefix" on May 29, 13:11, "Smith1, Robert E" writes:] > Hi, > > I am trying to install sqlite3 on Sun Solaris 2.8. I am not root so I > cannot install to /usr/local. I start configure with > --prefix=/ptmp/usr/localto try to get it to install to a different >

RE: [sqlite] Re: CAST

> -Original Message- > From: John Stanton [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 29, 2007 3:56 PM > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] Re: CAST > > You are looking for a fit to one particular restrictive, proprietary > environment. Our approach has been to work

Re: [sqlite] Re: CAST

Robert Simpson wrote: -Original Message- From: John Stanton [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 29, 2007 8:40 AM To: sqlite-users@sqlite.org Subject: Re: [sqlite] Re: CAST You have just given an excellent explanation of why the wrapper approach is flawed. Think about it.

Re: [sqlite] Problem using loadable extensions

> I'd like to figure out why the example > with half function which was provided by sqlite team can't be loaded as a > shared library. Yeah, it's poorly documented. I'll just put this in the wiki: http://www.sqlite.org/cvstrac/wiki?p=LoadableExtensions=1180475067=1 How To Build a Loadable

RE: [sqlite] --prefix

Sorry, my mistake: I didn't notice the "ptmp" prefix. Reminder to self: don't post without a proper night's sleep. We install SQLite3 to a custom path here (on Solaris, without Tcl support enabled) with no problem, so I don't know what's happening in your situation. -- James > -Original

Re: [sqlite] --prefix

I've run into a similar problem today and as far as I can see it has something to do with tcl extensions. If I run configure using --disable-tcl, then my 'make install' puts everything into the location specified using prefix. But in the case of tcl extensions 'make install' attempts to put

RE: [sqlite] --prefix

Why isn't it trying to install to /ptmp/usr/local since that is the value I gave --prefix?? -Original Message- From: James Dennett [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 29, 2007 1:44 PM To: sqlite-users@sqlite.org Subject: RE: [sqlite] --prefix > -Original Message- >

RE: [sqlite] --prefix

> -Original Message- > From: Smith1, Robert E [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 29, 2007 1:12 PM > To: sqlite-users@sqlite.org > Subject: [sqlite] --prefix > > Hi, > > I am trying to install sqlite3 on Sun Solaris 2.8. I am not root so I > cannot install to /usr/local. I

[sqlite] --prefix

Hi, I am trying to install sqlite3 on Sun Solaris 2.8. I am not root so I cannot install to /usr/local. I start configure with --prefix=/ptmp/usr/localto try to get it to install to a different directory. But I get the same error: /ptmp/bld/> make install tclsh

Re: [sqlite] using vacuum

If there is no redundancy to remove then the database size will remain the same. Vacuum is only really effective after you delete a large amount of data from a DB. - Scott Li, Charles wrote: > Hi, > I use the vacuum command on a database, but the size remains the same. What > should I check? >

[sqlite] using vacuum

Hi, I use the vacuum command on a database, but the size remains the same. What should I check? Thanks, Charles Li

Re: [sqlite] Re: CAST

I agree as well. We are upgrading a large, old application originally written almost 20 years ago. The additional time necessary for the most elegant solution can be very expensive. PCs today are powerful and cheap. The end user does not care if there is another layer inside, he only wants

RE: [sqlite] Re: CAST

Actually I'd say he gave a great explanation of why the wrapper approach is so important. Robert went through all the work to make SQLite perform in a scenario compatible with many other databases so now the users of his wrapper don't have to. Saying not to use wrappers when programming in

Re: [sqlite] Problem using loadable extensions

On 5/24/07, Joe Wilson <[EMAIL PROTECTED]> wrote: --- Alexander Smondyrev <[EMAIL PROTECTED]> wrote: > I am trying to use loadable extensions in Sqlite and I've run into the > following 2 problems: > > 1) I've downloaded src for 3.3.17 Sqlite and build it, but the '.load' > option does not seem

RE: [sqlite] How to restrict the peak heap usage during multiple inserts and updates?

I think I know what's going on. When you insert new rows in the presence of indexes then sqlite must touch a lot of pages in each trascation to satisfy the rebuilding of the index(es). These pages are built up in the transaction log which is stored in temp_store, which happens to be memory in

RE: [sqlite] Re: CAST

> -Original Message- > From: John Stanton [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 29, 2007 8:40 AM > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] Re: CAST > > You have just given an excellent explanation of why the wrapper > approach > is flawed. Think about it. Every

RE: [sqlite] How to restrict the peak heap usage during multiple inserts and updates?

The default is auto-commit, so unless you've opened an explicit transaction with BEGIN and do a number of inserts, the COMMIT suggestion is not useful in reducing memory footprint. (apologies in advance if this is obvious...) SDRAM is the normal volatile RAM, right? You know that temp_store is

RE: [sqlite] How to restrict the peak heap usage during multiple inserts and updates?

Kalyani Tummala uttered: I am planning to use sqlite as a database for storing and retrieving media data of about 5-10k records in a device whose main memory is extremely small. A sequence of insert statements increasing the heap usage to nearly 70K(almost saturating point) which is crashing my

Re: [sqlite] How to restrict the peak heap usage during multiple inserts and updates?

In your case we would not use Sqlite and instead use a much simpler storage method. Since your storage appears to be RAM resident that approach is indicated a fortiori. We have had success with using storage based on AVL trees. It is very fast and remains so despite repeated insertions and

Re: [sqlite] Re: CAST

Robert Simpson wrote: -Original Message- From: John Stanton [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 29, 2007 6:18 AM To: sqlite-users@sqlite.org Subject: Re: [sqlite] Re: CAST Your comments endorse the approach we took which was to avoid the wrapper concept entirely with its

RE: [sqlite] How to restrict the peak heap usage during multiple inserts and updates?

Hi John, I could not understand your query properly. Let me tell you my application scenario. I am planning to use sqlite as a database for storing and retrieving media data of about 5-10k records in a device whose main memory is extremely small. A sequence of insert statements increasing the

[sqlite] Memory and Performance Profiling of sqlite commands

Dear Group, Is there any provision in the sqlite library for memory and performance profiling of SQL commands. How can I use the test folder where tcl script files are available for regression testing? How can I run those scripts in Windows XP? Thanks in advance Kalyani

RE: [sqlite] Re: CAST

> -Original Message- > From: John Stanton [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 29, 2007 6:18 AM > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] Re: CAST > > Your comments endorse the approach we took which was to avoid the > wrapper concept entirely with its inherent

Re: [sqlite] How to restrict the peak heap usage during multiple inserts and updates?

Since you are only using part of Sqlite have you considered using a much smaller footprint storage system which only implements the functions you are using? Kalyani Tummala wrote: Hi joe, Thanks for your response. In order to reduce the footprint size, I have bypassed parser completely

Re: [sqlite] Join

See the ATTACH statement. Shilpa Sheoran wrote: Does sqlite allow joining tables in different database files using triggers or any other mechanism? Does it affect the performance? Thanks Shilpa - To unsubscribe,

Re: [sqlite] Re: CAST

Robert Simpson wrote: -Original Message- From: John Stanton [mailto:[EMAIL PROTECTED] Sent: Monday, May 28, 2007 4:21 PM To: sqlite-users@sqlite.org Subject: Re: [sqlite] Re: CAST We actually do that with our Sqlite interfaces. We use the declared type to specify the type and perform a

[sqlite] Re: sqlite3_reset (or sqlite3_finalize) and error reporting?

Scott McDonald wrote: Jef Driesen wrote: Scott McDonald wrote: Jef Driesen wrote: I have some questions on the usage of sqlite3_reset (or sqlite3_finalize) after sqlite3_step. In the legacy interface I use sqlite3_reset after sqlite3_step to obtain a more specific error code for

Re: [sqlite] how to change SQLite column definition

Thanks! But it will take a long time if the table have a large number of rows. I hope that SQLite will support "Alter Column" in next version! - Original Message - From: "Scott Hess" <[EMAIL PROTECTED]> To: Sent: Monday, May 28, 2007 10:38 PM Subject: Re: