[sqlite] Version 3.2.8 and 2.8.17

[Prettina Louis]

hello sir,

 Greetings in the name of the lord!


  Sir, please let me know , if I can download and configure the Sqlite 3 in 
irix 6.5.. I would be highly grateful to you. 

 Thanks in advance

  "praise the lord!"

With regards and prayers,
prettina

===
Ms. Prettina Anto Louis
Junior Research Fellow
C/O Dr. Z.A. Rafi.,(Reader)
Bioinformatics Centre
School of Biotechnology
Madurai Kamaraj University
Madurai-625021
Cell : 9842258238
email: [EMAIL PROTECTED]

re: [sqlite] VB.Net

[sales]

We did try one wrapper designed for .NET but it's setup program didn't set 
itself up right on our system and I didn't have the time to mess with it.

We do use this and it works great: http://www.sqliteplus.com/   It's a COM 
interface to a sqlite DLL.

It's a little pricey at $180 but that includes a database manager interface and 
a grid tool too. Not too bad at all.

The thing that helped the most was reading the Windows performance tips page on 
the sqlite web site.

Tom


 From: Vishal Kashyap <[EMAIL PROTECTED]>
Sent: Monday, December 19, 2005 1:33 PM
To: sqlite-users@sqlite.org
Subject: [sqlite] VB.Net 

Dear All ,

Any possibility of using VB.NET with Sqlite as Backend.

Please do mention some links.

--
With Best Regards,
Vishal Kashyap.
http://vishalkashyap.tk

re: Re[2]: [sqlite] multiple Db's and journal file time hit?

[sales]

Thank you for your tips on page file settings. 

This is going to end up as a commerical product and it can be difficult to 
predict what potential users may have and what other programs they might try to 
run the same time as mine in the background.

Our application runs up to 20 threads and is pretty I/O intensive, we do advise 
them to run it at night or when the system won't be too busy-- but we cannot 
force them and I hesitate to attempt to alter their system.

It's a delicate balance, however, when using sqlite we notice memory usage 
stays nice and low and processing flows right along. Also, we were using an 
in-house, file system based processing history with filenames being the actual 
hash codes. It worked great until a user decided he wanted to delete 2.8 
million items. That took many, many hours and other databases such as Microsoft 
Access were too bulky for internet download/setup.

Hello SQLITE. :-)

Thanks for your memory and page file advice. That is what is going on with the 
hash tables.

Tom


 From: Teg <[EMAIL PROTECTED]>
Sent: Monday, December 19, 2005 1:24 PM
To: "[EMAIL PROTECTED]" 
Subject: Re[2]: [sqlite] multiple Db's and journal file time hit? 

Hello sales,

What are you using for a data structure? I regularly have literally
millions of hashed data structures in memory without encountering this.
If it's windows, I know exactly what it is though, windows pages
things out on a whim so, if you're not constantly touching your data
structures, they get paged out. It's easy to tell if you've been
paged, turn on the VM column in task manager and compare memory usage
to virtual memory size. If there's a large difference then there you
go.

One solution I've used, is to simply disable the page file and add
more RAM. In that way windows can't page your app out. With 2G of
memory and no page file, I never run out even when running games.

I use "hash_sets" for my hashed data structures. I use the one that
comes with STLPort. I'm not suggesting not using SQLite, I am
suggesting that 250K hashes isn't really that many.

C

Monday, December 19, 2005, 4:02:24 PM, you wrote:

stc> Yes the timestamp method is one we have done from within
stc> our own code and it may very well be the operating system
stc> catching up to where it should be and not the database's fault at
stc> all.

stc> It hangs on a read after the inserts--- ourDB.Exec("Select
stc> x From Y where x.HashCode = z LIMIT 1;"). 

stc> (where x.HashCode is unique.)

stc> Originally we were just storing all hash codes in memory
stc> but on our text box (512MB RAM/4 GIG VRam/40G HD) after about
stc> 250,000 hashcodes (32 bit signed integers) we encountered wicked
stc> memory thrashing (physical / virtual) to the point where the
stc> system would (appear to) lock up and had to abandon the idea for
stc> the database.

stc> It eventually does complete, the first time it takes about
stc> 30 seconds and does not generate any errors. After that one time
stc> we can hit the database 10-20 times a second with no problems for
stc> over 12 hours (length of our test).

stc> Again it may very well be the operating system catching up
stc> to where it should be and not the database's fault at all.

stc> Thanks for all your good advice.

stc> Tom

stc> 
stc> From: Dennis Jenkins 
stc> Sent: Monday, December 19, 2005 11:25 AM
stc> To: sqlite-users@sqlite.org
stc> Subject: Re: [sqlite] multiple Db's and journal file time hit? 

stc> [EMAIL PROTECTED] wrote:

>>The delay seems to coincide with the journal file creation-- it
>>happens after our first (committed but not yet written to disk)
>>write attempt to the database, the journal file does not at-the-time
>>exist, and there are 500+ inserts pending with reads rapidly being
>>added after that.
>>
>>Although I too have seen anti-virus programs hose things up, we
>>don't have any running. It was a good thing to check for though. 
>>
>>We can live with this minor start-up penalty because our users
>>will oftentimes run this app 12-36 hours straight and could end up
>>hitting the database 1,000,000 times in that period.
>>
>>It does not appear to be any kind of error as no exceptions are
>>thrown. We can create a minor user-appreciated perception of
>>busyness on-screen. :-)
>>
>>Tom
>>
>>
>> From: [EMAIL PROTECTED]
>>Sent: Monday, December 19, 2005 8:59 AM
>>To: sqlite-users@sqlite.org
>>Subject: Re: [sqlite] multiple Db's and journal file time hit? 
>>
>>[EMAIL PROTECTED] wrote:
>> 
>>
>>>We just noticed a 30-40 second hit at early on in our program running. >
>>> 
>>>
>>
>>Others have reported things like this caused by anti-virus
>>software running on the same machine and insisting on doing
>>some kind of virus scan the first time the journal file is
>>created.
>>--
>>D. Richard Hipp 
>> 
>>

stc> A few suggestions:

stc> White box it:
stc> Compile SQLITE 

Re: [sqlite] VB.Net

[Robert Simpson]

- Original Message - 
From: "Vishal Kashyap" <[EMAIL PROTECTED]>


Any possibility of using VB.NET with Sqlite as Backend.

Please do mention some links.


http://www.sqlite.org/cvstrac/wiki?p=SqliteWrappers

Lots to choose from ... 


Robert

Re: [sqlite] VB.Net

[Cory Nelson]

check out the sqlitewrappers wiki page.

On 12/19/05, Vishal Kashyap <[EMAIL PROTECTED]> wrote:
> Dear All ,
>
> Any possibility of using VB.NET with Sqlite as Backend.
>
> Please do mention some links.
>
>
> --
> With Best Regards,
> Vishal Kashyap.
> http://vishalkashyap.tk
>


--
Cory Nelson
http://www.int64.org

[sqlite] VB.Net

[Vishal Kashyap]

Dear All ,

Any possibility of using VB.NET with Sqlite as Backend.

Please do mention some links.


--
With Best Regards,
Vishal Kashyap.
http://vishalkashyap.tk

Re[2]: [sqlite] multiple Db's and journal file time hit?

[Teg]

Hello drh,

I'll try to characterize what I see. I'm running bare-backed here, no
firewall or virus scanner (though I'm protected from the internet by a
hardware firewall).

Some of my databases are pushing 10gig but, I see it on smaller ones
too, or at least I think I see it.

C

Monday, December 19, 2005, 11:57:52 AM, you wrote:

dhc> [EMAIL PROTECTED] wrote:
>> 
>> We just noticed a 30-40 second hit at early on in our program running. >

dhc> Others have reported things like this caused by anti-virus
dhc> software running on the same machine and insisting on doing
dhc> some kind of virus scan the first time the journal file is
dhc> created.
dhc> --
dhc> D. Richard Hipp <[EMAIL PROTECTED]>




-- 
Best regards,
 Tegmailto:[EMAIL PROTECTED]

Re[2]: [sqlite] multiple Db's and journal file time hit?

[Teg]

Hello sales,

What are you using for a data structure? I regularly have literally
millions of hashed data structures in memory without encountering this.
If it's windows, I know exactly what it is though, windows pages
things out on a whim so, if you're not constantly touching your data
structures, they get paged out. It's easy to tell if you've been
paged, turn on the VM column in task manager and compare memory usage
to virtual memory size. If there's a large difference then there you
go.

One solution I've used, is to simply disable the page file and add
more RAM. In that way windows can't page your app out. With 2G of
memory and no page file, I never run out even when running games.

I use "hash_sets" for my hashed data structures. I use the one that
comes with STLPort. I'm not suggesting not using SQLite, I am
suggesting that 250K hashes isn't really that many.

C

Monday, December 19, 2005, 4:02:24 PM, you wrote:

stc> Yes the timestamp method is one we have done from within
stc> our own code and it may very well be the operating system
stc> catching up to where it should be and not the database's fault at
stc> all.

stc> It hangs on a read after the inserts--- ourDB.Exec("Select
stc> x From Y where x.HashCode = z LIMIT 1;"). 

stc> (where x.HashCode is unique.)

stc> Originally we were just storing all hash codes in memory
stc> but on our text box (512MB RAM/4 GIG VRam/40G HD) after about
stc> 250,000 hashcodes (32 bit signed integers) we encountered wicked
stc> memory thrashing (physical / virtual) to the point where the
stc> system would (appear to) lock up and had to abandon the idea for
stc> the database.

stc> It eventually does complete, the first time it takes about
stc> 30 seconds and does not generate any errors. After that one time
stc> we can hit the database 10-20 times a second with no problems for
stc> over 12 hours (length of our test).

stc> Again it may very well be the operating system catching up
stc> to where it should be and not the database's fault at all.

stc> Thanks for all your good advice.

stc> Tom

stc> 
stc>  From: Dennis Jenkins <[EMAIL PROTECTED]>
stc> Sent: Monday, December 19, 2005 11:25 AM
stc> To: sqlite-users@sqlite.org
stc> Subject: Re: [sqlite] multiple Db's and journal file time hit? 

stc> [EMAIL PROTECTED] wrote:

>>The delay seems to coincide with the journal file creation-- it
>>happens after our first (committed but not yet written to disk)
>>write attempt to the database, the journal file does not at-the-time
>>exist, and there are 500+ inserts pending with reads rapidly being
>>added after that.
>>
>>Although I too have seen anti-virus programs hose things up, we
>>don't have any running. It was a good thing to check for though. 
>>
>>We can live with this minor start-up penalty because our users
>>will oftentimes run this app 12-36 hours straight and could end up
>>hitting the database 1,000,000 times in that period.
>>
>>It does not appear to be any kind of error as no exceptions are
>>thrown. We can create a minor user-appreciated perception of
>>busyness on-screen. :-)
>>
>>Tom
>>
>>
>> From: [EMAIL PROTECTED]
>>Sent: Monday, December 19, 2005 8:59 AM
>>To: sqlite-users@sqlite.org
>>Subject: Re: [sqlite] multiple Db's and journal file time hit? 
>>
>>[EMAIL PROTECTED] wrote:
>> 
>>
>>>We just noticed a 30-40 second hit at early on in our program running. >
>>> 
>>>
>>
>>Others have reported things like this caused by anti-virus
>>software running on the same machine and insisting on doing
>>some kind of virus scan the first time the journal file is
>>created.
>>--
>>D. Richard Hipp 
>> 
>>

stc> A few suggestions:

stc> White box it:
stc> Compile SQLITE yourself with debugging symbols. Run your code in a
stc> profiler. Then run it again in a debugger examine the regions of code
stc> that the profiler flagged as "taking a long time".

stc> Black box it:
stc> Use "filemon" (win32/64, from www.sysinternals.com) or "strace" on Linux
stc> or the equivilent on any other platform. They will timestamp and record
stc> all disk access. Have your own program display the exact system 
stc> timestamps before and after the lengthy operation. Examine the logs to
stc> see what is going on.





-- 
Best regards,
 Tegmailto:[EMAIL PROTECTED]

[sqlite] implementing editable result sets

[Will Leshner]

Hi. I apologize in advance for the length of this question, but it is  
a little involved.


I am the author of a wrapper for SQLite and in that wrapper there is  
an object called a RecordSet that represents the results of a query.  
One of the things you can do with a RecordSet is edit records. The  
way I've implemented editing a RecordSet is to construct an UPDATE  
statement based on the new values for the fields of the record. The  
problem, though, is that while query results are always returned in  
the form of a RecordSet, not all RecordSets represent query results  
that are really editable in any meaningful way. The big problem is  
knowing which record is really being represented by a particular row  
in a RecordSet object. What I do is add a rowid column to every  
query. For many queries, this results in a syntax error. For example,  
if the query involves joins and such. That's exactly what I want to  
have happen. If I get a syntax error, then I know the results of the  
query aren't really something I want to let the user edit, so I  
requery without the rowid and just remember that the resulting  
RecordSet isn't editable. The problem, however, is that some queries  
allow a rowid column, but still shouldn't be editable. For example:


SELECT rowid,count(rowid) FROM table

One might argue that such a query should return an error, but even if  
it did, I couldn't rely on it, because this query is perfectly fine:


SELECT rowid,count(rowid) FROM table GROUP BY rowid

So, the question I have is this: Is there some way I can determine,  
short of parsing the SQL for myself, that the results of a query are  
"suitable for editing"? I think, by "suitable for editing", that I  
mean the results all come from one table and only include natural  
columns of that table. I'm perfectly happy to detect "suitability"  
during the execution of the VM. I have my own loop where I call  
sqlite3_step and such, if that makes any difference. For example, if  
I had a way to know, during the execution of the VM, that the results  
were coming from more than one table at the same time, that would  
certainly be a big step in the right direction.


A related topic is the ability to get the rowid of the rows returned  
by a query without having to add the 'rowid' column explicitly. Right  
now I manually add 'rowid' in the wrapper, but I really hate doing  
that because I'd like to touch the user's SQL as little as possible.  
I think it would be really cool if there were a way to tell SQLite to  
return, along with the regular results, the rowid for each row. If  
'rowid' makes no sense for the query, then maybe SQLite could return  
some kind of ILLEGAL_ROWID value. Would anybody else find such a  
thing useful?


Thanks.

Re: [sqlite] multiple Db's and journal file time hit?

[sales]

Yes the timestamp method is one we have done from within our own code and it 
may very well be the operating system catching up to where it should be and not 
the database's fault at all.

It hangs on a read after the inserts--- ourDB.Exec("Select x From Y where 
x.HashCode = z LIMIT 1;"). 

(where x.HashCode is unique.)

Originally we were just storing all hash codes in memory but on our text box 
(512MB RAM/4 GIG VRam/40G HD) after about 250,000 hashcodes (32 bit signed 
integers) we encountered wicked memory thrashing (physical / virtual) to the 
point where the system would (appear to) lock up and had to abandon the idea 
for the database.

It eventually does complete, the first time it takes about 30 seconds and does 
not generate any errors. After that one time we can hit the database 10-20 
times a second with no problems for over 12 hours (length of our test).

Again it may very well be the operating system catching up to where it should 
be and not the database's fault at all.

Thanks for all your good advice.

Tom


 From: Dennis Jenkins <[EMAIL PROTECTED]>
Sent: Monday, December 19, 2005 11:25 AM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] multiple Db's and journal file time hit? 

[EMAIL PROTECTED] wrote:

>The delay seems to coincide with the journal file creation-- it happens after 
>our first (committed but not yet written to disk) write attempt to the 
>database, the journal file does not at-the-time exist, and there are 500+ 
>inserts pending with reads rapidly being added after that.
>
>Although I too have seen anti-virus programs hose things up, we don't have any 
>running. It was a good thing to check for though. 
>
>We can live with this minor start-up penalty because our users will oftentimes 
>run this app 12-36 hours straight and could end up hitting the database 
>1,000,000 times in that period.
>
>It does not appear to be any kind of error as no exceptions are thrown. We can 
>create a minor user-appreciated perception of busyness on-screen. :-)
>
>Tom
>
>
> From: [EMAIL PROTECTED]
>Sent: Monday, December 19, 2005 8:59 AM
>To: sqlite-users@sqlite.org
>Subject: Re: [sqlite] multiple Db's and journal file time hit? 
>
>[EMAIL PROTECTED] wrote:
> 
>
>>We just noticed a 30-40 second hit at early on in our program running. > 
>> 
>>
>
>Others have reported things like this caused by anti-virus
>software running on the same machine and insisting on doing
>some kind of virus scan the first time the journal file is
>created.
>--
>D. Richard Hipp 
> 
>

A few suggestions:

White box it:
Compile SQLITE yourself with debugging symbols. Run your code in a 
profiler. Then run it again in a debugger examine the regions of code 
that the profiler flagged as "taking a long time".

Black box it:
Use "filemon" (win32/64, from www.sysinternals.com) or "strace" on Linux 
or the equivilent on any other platform. They will timestamp and record 
all disk access. Have your own program display the exact system 
timestamps before and after the lengthy operation. Examine the logs to 
see what is going on.

Re: [sqlite] Version 3.2.8 and 2.8.17

[drh]

[EMAIL PROTECTED] wrote:
> [EMAIL PROTECTED] writes:
> 
> > New versions of SQLite 2 and 3 are now available on the website.
> >
> >   http://www.sqlite.org/
> >
> > These new versions contain a one-line fix to a problem that can
> > lead to database corruption.  The problem has been in the code
> > for almost 4 years and has so far gone unnoticed, suggesting that
> > it is not a serious concern.  But because it can lead to database
> > corruption, upgrading is recommended.
> 
> The source file 2.8.17.tar.gz available on the download page is only 45 bytes
> long.  I think that's a bit incomplete. :-)
> 
> Also, any chance you could post (or email me, if it's not of general interest)
> the small patch to 2.8.16 that generated this version (or give me the CVS
> command or revision id's to determine the difference in the 2.8 branch)?
> 

I have a backlog today.  I will fix the build problems as I am
able, but you might have to wait a few days.

The patch is http://www.sqlite.org/cvstrac/chngview?cn=2832

You can always get the latest patches by visiting the timeline.
http://www.sqlite.org/cvstrac/timeline

--
D. Richard Hipp <[EMAIL PROTECTED]>

Re: [sqlite] multiple Db's and journal file time hit?

[Dennis Jenkins]

[EMAIL PROTECTED] wrote:


The delay seems to coincide with the journal file creation-- it happens after 
our first (committed but not yet written to disk) write attempt to the 
database, the journal file does not at-the-time exist, and there are 500+ 
inserts pending with reads rapidly being added after that.

Although I too have seen anti-virus programs hose things up, we don't have any running. It was a good thing to check for though. 


We can live with this minor start-up penalty because our users will oftentimes 
run this app 12-36 hours straight and could end up hitting the database 
1,000,000 times in that period.

It does not appear to be any kind of error as no exceptions are thrown. We can 
create a minor user-appreciated perception of busyness on-screen. :-)

Tom


From: [EMAIL PROTECTED]
Sent: Monday, December 19, 2005 8:59 AM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] multiple Db's and journal file time hit? 


[EMAIL PROTECTED] wrote:
 

We just noticed a 30-40 second hit at early on in our program running. > 
   



Others have reported things like this caused by anti-virus
software running on the same machine and insisting on doing
some kind of virus scan the first time the journal file is
created.
--
D. Richard Hipp 
 



A few suggestions:

White box it:
Compile SQLITE yourself with debugging symbols.  Run your code in a 
profiler.  Then run it again in a debugger examine the regions of code 
that the profiler flagged as "taking a long time".


Black box it:
Use "filemon" (win32/64, from www.sysinternals.com) or "strace" on Linux 
or the equivilent on any other platform.  They will timestamp and record 
all disk access.  Have your own program display the exact system 
timestamps before and after the lengthy operation.  Examine the logs to 
see what is going on.

Re: [sqlite] multiple Db's and journal file time hit?

[sales]

The delay seems to coincide with the journal file creation-- it happens after 
our first (committed but not yet written to disk) write attempt to the 
database, the journal file does not at-the-time exist, and there are 500+ 
inserts pending with reads rapidly being added after that.

Although I too have seen anti-virus programs hose things up, we don't have any 
running. It was a good thing to check for though. 

We can live with this minor start-up penalty because our users will oftentimes 
run this app 12-36 hours straight and could end up hitting the database 
1,000,000 times in that period.

It does not appear to be any kind of error as no exceptions are thrown. We can 
create a minor user-appreciated perception of busyness on-screen. :-)

Tom


 From: [EMAIL PROTECTED]
Sent: Monday, December 19, 2005 8:59 AM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] multiple Db's and journal file time hit? 

[EMAIL PROTECTED] wrote:
> 
> We just noticed a 30-40 second hit at early on in our program running. > 

Others have reported things like this caused by anti-virus
software running on the same machine and insisting on doing
some kind of virus scan the first time the journal file is
created.
--
D. Richard Hipp 

Re: [sqlite] Version 3.2.8 and 2.8.17

[Derrell . Lipman]

[EMAIL PROTECTED] writes:

> New versions of SQLite 2 and 3 are now available on the website.
>
>   http://www.sqlite.org/
>
> These new versions contain a one-line fix to a problem that can
> lead to database corruption.  The problem has been in the code
> for almost 4 years and has so far gone unnoticed, suggesting that
> it is not a serious concern.  But because it can lead to database
> corruption, upgrading is recommended.

The source file 2.8.17.tar.gz available on the download page is only 45 bytes
long.  I think that's a bit incomplete. :-)

Also, any chance you could post (or email me, if it's not of general interest)
the small patch to 2.8.16 that generated this version (or give me the CVS
command or revision id's to determine the difference in the 2.8 branch)?

Thanks!

Derrell

Re: [sqlite] Version 3.2.8 and 2.8.17

[Gerry Snyder]

[EMAIL PROTECTED] wrote:


New versions of SQLite 2 and 3 are now available on the website.

 http://www.sqlite.org/

 



Is the omission of tcl bindings for 2.8.17 deliberate? They are not 
listed for either linux or Windows.

Re: Re[2]: [sqlite] multiple Db's and journal file time hit?

[Will Leshner]

On Dec 19, 2005, at 8:32 AM, Teg wrote:


I notice a similar thing with my databases when they get to any decent
size. it seems like the first time you access them, doing anything,
there's a decent startup delay and then it's fast from that time
forward. Someone mentioned OS disk cache and I wonder about the
internal SQLite cache too.



Define "decent size". I've never seen any significant delay opening  
any SQLite database. But I don't have databases that are gigabytes  
big, so maybe I've just never run into the problem.

Re[2]: [sqlite] multiple Db's and journal file time hit?

[Teg]

Hello sales,

I notice a similar thing with my databases when they get to any decent
size. it seems like the first time you access them, doing anything,
there's a decent startup delay and then it's fast from that time
forward. Someone mentioned OS disk cache and I wonder about the
internal SQLite cache too.

I'm using the library directly within a program though.

C


Monday, December 19, 2005, 11:17:14 AM, you wrote:

stc> I think I've confused the issue a bit and the
stc> aforementioned time hit might be normal given:
stc> http://www.sqlite.org/lockingv3.html 

stc> We are using a separately developed COM DLL interface to
stc> Sqlite v3: http://www.sqliteplus.com/ 

stc> And we can live with the journal creation time if that is what it is.

stc> Tom

stc> 
stc>  From: [EMAIL PROTECTED]
stc> Sent: Monday, December 19, 2005 6:43 AM
stc> To: sqlite-users@sqlite.org
stc> Subject: [sqlite] multiple Db's and journal file time hit? 

stc> Hello

stc> Recently it was written: whenever a modifying transaction starts (or 
rather, when it
stc> has to actually write data to disk for the first time), SQLite has to
stc> create a journal file for each DB involved as well as a master journal
stc> file. 

stc> We are testing (almost ready to purchase the $180 COM
stc> version) and have just noticed a 30-40 second hit at early on in
stc> our program running. It happens when accessing the databases but
stc> not always the same call and we are wondering if it might be
stc> related to journal file start up time OR if there is some kind of
stc> built-in pause or delay in the demo version. 

stc> Background: 

stc> a) We use two databases- one for a current run and one for long-term 
history.
stc> b) The historical database has two tables with two indexes
stc> (an integer (hash code) and a date column) and is set to
stc> synchronous = Normal
stc> c) The current-run database has one table with two indexes
stc> (an integer (hash code) and another integer) and is set to
stc> synchronous = OFF. Note: we blow away the current-run database
stc> each time a certain process is kicked off and there is never more
stc> than one current-run db-- so if the data is lost from the current
stc> run it is no big deal.
stc> d) It is a Win32 application and PRAGMA page_size = 4096.
stc> e) System memory is 512MB and PRAGMA cache_size = 65536
stc> f) Inserts are bundled into one transaction, sometimes as
stc> many as 800 at a shot before .Exec(COMMIT) is called.
stc> g) No database error codes were generated.
stc> h) There are no other programs running when our application
stc> is running and Windows Task Manager (processes and performance)
stc> shows no unusual activity. 

stc> Description: Program runs, inserts between 500 and 800
stc> records into the current-run db, and then at various points in
stc> reads/inserts (within 10 seconds after the first big insert) the
stc> 30-40 second hit will occur.

stc> Important note: once that 30-40 second hit is done the
stc> program runs great-- for up to 12 hours in fact doing hundreds of
stc> thousands of transactions and with great speed. And it only
stc> stopped after 12 hours because we completed our tests.

stc> We want to buy it but are concerned about the 30-40 second hit.

stc> Anyone got an idea what might be going on?

stc> Thanks much,

stc> Tom Nicholas
stc> http://www.thntech.com 





-- 
Best regards,
 Tegmailto:[EMAIL PROTECTED]

re: [sqlite] multiple Db's and journal file time hit?

[sales]

I think I've confused the issue a bit and the aforementioned time hit might be 
normal given:
http://www.sqlite.org/lockingv3.html 

We are using a separately developed COM DLL interface to Sqlite v3: 
http://www.sqliteplus.com/ 

And we can live with the journal creation time if that is what it is.

Tom


 From: [EMAIL PROTECTED]
Sent: Monday, December 19, 2005 6:43 AM
To: sqlite-users@sqlite.org
Subject: [sqlite] multiple Db's and journal file time hit? 

Hello

Recently it was written: whenever a modifying transaction starts (or rather, 
when it 
has to actually write data to disk for the first time), SQLite has to 
create a journal file for each DB involved as well as a master journal 
file. 

We are testing (almost ready to purchase the $180 COM version) and have just 
noticed a 30-40 second hit at early on in our program running. It happens when 
accessing the databases but not always the same call and we are wondering if it 
might be related to journal file start up time OR if there is some kind of 
built-in pause or delay in the demo version. 

Background: 

a) We use two databases- one for a current run and one for long-term history.
b) The historical database has two tables with two indexes (an integer (hash 
code) and a date column) and is set to synchronous = Normal
c) The current-run database has one table with two indexes (an integer (hash 
code) and another integer) and is set to synchronous = OFF. Note: we blow away 
the current-run database each time a certain process is kicked off and there is 
never more than one current-run db-- so if the data is lost from the current 
run it is no big deal.
d) It is a Win32 application and PRAGMA page_size = 4096.
e) System memory is 512MB and PRAGMA cache_size = 65536
f) Inserts are bundled into one transaction, sometimes as many as 800 at a shot 
before .Exec(COMMIT) is called.
g) No database error codes were generated.
h) There are no other programs running when our application is running and 
Windows Task Manager (processes and performance) shows no unusual activity. 

Description: Program runs, inserts between 500 and 800 records into the 
current-run db, and then at various points in reads/inserts (within 10 seconds 
after the first big insert) the 30-40 second hit will occur.

Important note: once that 30-40 second hit is done the program runs great-- for 
up to 12 hours in fact doing hundreds of thousands of transactions and with 
great speed. And it only stopped after 12 hours because we completed our tests.

We want to buy it but are concerned about the 30-40 second hit.

Anyone got an idea what might be going on?

Thanks much,

Tom Nicholas
http://www.thntech.com 

[sqlite] multiple Db's and journal file time hit?

[sales]

Hello

Recently it was written: whenever a modifying transaction starts (or rather, 
when it 
has to actually write data to disk for the first time), SQLite has to 
create a journal file for each DB involved as well as a master journal 
file. 

We are testing (almost ready to purchase the $180 COM version) and have just 
noticed a 30-40 second hit at early on in our program running. It happens when 
accessing the databases but not always the same call and we are wondering if it 
might be related to journal file start up time OR if there is some kind of 
built-in pause or delay in the demo version. 

Background: 

a) We use two databases- one for a current run and one for long-term history.
b) The historical database has two tables with two indexes (an integer (hash 
code) and a date column) and is set to synchronous = Normal
c) The current-run database has one table with two indexes (an integer (hash 
code) and another integer) and is set to synchronous = OFF. Note: we blow away 
the current-run database each time a certain process is kicked off and there is 
never more than one current-run db-- so if the data is lost from the current 
run it is no big deal.
d) It is a Win32 application and PRAGMA page_size = 4096.
e) System memory is 512MB and PRAGMA cache_size = 65536
f) Inserts are bundled into one transaction, sometimes as many as 800 at a shot 
before .Exec(COMMIT) is called.
g) No database error codes were generated.
h) There are no other programs running when our application is running and 
Windows Task Manager (processes and performance) shows no unusual activity. 

Description: Program runs, inserts between 500 and 800 records into the 
current-run db, and then at various points in reads/inserts (within 10 seconds 
after the first big insert) the 30-40 second hit will occur.

Important note: once that 30-40 second hit is done the program runs great-- for 
up to 12 hours in fact doing hundreds of thousands of transactions and with 
great speed. And it only stopped after 12 hours because we completed our tests.

We want to buy it but are concerned about the 30-40 second hit.

Anyone got an idea what might be going on?

Thanks much,

Tom Nicholas
http://www.thntech.com

RE: [sqlite] Reg: Sqlite Installation

[Essien Ita Essien]

Hi Prettina,

It would *really* help, if you included a snip of the *actual* error you're
having. Then folks would be able to help out. As it is, I don't think
there's an *SQLite3 For IRIX Installation Howto(tm)* anywhere on the
Googlesphere ;)

A picture is worth a thousand words... but when in doubt, send in a thousand
lines of error!
- Anon (aka... ME)

Essien Ita Essien
-
http://essiene.blogspot.com
http://datavibe.net/~essiene
http://datavibe.net/~essiene/pysystray
--
...the future is open.


-Original Message-
From: Prettina Louis [mailto:[EMAIL PROTECTED] 
Sent: Monday, December 19, 2005 1:12 PM
To: sqlite-users@sqlite.org
Subject: [sqlite] Reg: Sqlite Installation

  
Respected Sir,


Greetings!


Sir, I am planning to install Sqlite for Kobas in Irix 6.5 OS, Please
let me know in detail how to install the same. I am facing problem after
configuration step, ie in 'make' step some error. I would be grateful to you
if u could give me a step wise details to install the same.

  Thanking you!

With regards,
prettina 

[sqlite] Reg: Sqlite Installation

[Prettina Louis]

  
Respected Sir,


Greetings!


Sir, I am planning to install Sqlite for Kobas in Irix 6.5 OS, Please let 
me know in detail how to install the same. I am facing problem after 
configuration step, ie in 'make' step some error. I would be grateful to you if 
u could give me a step wise details to install the same.

  Thanking you!

With regards,
prettina