Re: [sqlite] SQLite 3.2.5 and Mac OSX network folders

hi all can you please tell me is their any sqlite source code available for the java rgds vidushi tandon --- Aaron Burghardt <[EMAIL PROTECTED]> wrote: > You can take a look at what Apple has done for OS X > here: > > http://www.opensource.apple.com/darwinsource/10.4/SQLite-28/ > >

Re: [sqlite] Re: Number of rows in a query result

Puneet Kishor wrote: Igor Tandetnik wrote: Alfredo Cole <[EMAIL PROTECTED]> wrote: In order to update a progress bar, I need to know the total number of rows returned by a query, similar to MySQL's mysql_num_rows. Is there a function like that in the C API? I may have overlooked it, but

Re: [sqlite] Number of rows in a query result

El Jueves, 27 de Octubre de 2005 15:44, Radu Lodina escribió: > Hi Alfredo, > > > I supose you don't use > sqlite3_get_tablefu >nction right ? > > > Call another query with: > SELECT COUNT(*) AS NrRecords FROM ( ) > > > Radu

Re: [sqlite] Re: Number of rows in a query result

Igor Tandetnik wrote: Alfredo Cole <[EMAIL PROTECTED]> wrote: In order to update a progress bar, I need to know the total number of rows returned by a query, similar to MySQL's mysql_num_rows. Is there a function like that in the C API? I may have overlooked it, but have not found it so far.

[sqlite] Re: Number of rows in a query result

Alfredo Cole <[EMAIL PROTECTED]> wrote: In order to update a progress bar, I need to know the total number of rows returned by a query, similar to MySQL's mysql_num_rows. Is there a function like that in the C API? I may have overlooked it, but have not found it so far. There is no such

Re: [sqlite] Number of rows in a query result

Hi Alfredo, I supose you don't use sqlite3_get_tablefunction right ? Call another query with: SELECT COUNT(*) AS NrRecords FROM ( ) Radu Lodina On 10/28/05, Alfredo Cole <[EMAIL PROTECTED]> wrote: > > Hi: > > In order to update a

[sqlite] Number of rows in a query result

Hi: In order to update a progress bar, I need to know the total number of rows returned by a query, similar to MySQL's mysql_num_rows. Is there a function like that in the C API? I may have overlooked it, but have not found it so far. Thank you. -- Alfredo J. Cole Grupo ACyC

Re: [sqlite] Size of INSERT and UPDATE in TRANSACTION

It would be the other way around, no? The larger the no of inserts within a Transaction, the better the performance. On 10/27/05, Hannes Ricklefs <[EMAIL PROTECTED]> wrote: > > Hello, > > I was wondering if anyone has any experience with the number of INSERT > UPDATE > statements in one

Re: [sqlite] Time scale on INSERT and UPDATE

Hannes Ricklefs wrote: Hello, does anyone have any experience in the amount of time increase for an UPDATE, INSERT, SELECT in relation to the size of the actual database? Is it proportional or exponential for example... Regards, Hannes Hannes, The execution time for inserts depends

Re: [sqlite] Time scale on INSERT and UPDATE

This depends on the number of indices. Insertions into a B-Tree essntially follow an Nlog(N) law, so the best you can expect is O(Nlog(N)). Similarly for deletions. A SELECT depends upon the query and indices. A row search is essentially linear with size, O(N), whereas a B-Tree index

Re: [sqlite] SQLite 3.2.5 and Mac OSX network folders

You can take a look at what Apple has done for OS X here: http://www.opensource.apple.com/darwinsource/10.4/SQLite-28/ Don't be mislead by the project name--it is SQLite 3. I haven't studied it closely, but it should allow you to build exactly what Apple shipped. The Makefile has

Re[2]: [sqlite] Time scale on INSERT and UPDATE

Hi, > with updates and selects, i would expect that the time of finding the > record(s) (to update or select) (the where-clause) depends on the size > of the table and on whether indexes are used. With indexing if the database has eg 65535 records, then maximum 17 comparisations. it is one more

Re: [sqlite] Time scale on INSERT and UPDATE

Hello Hannes, in my experience, the time of inserts does not grow with the size of the database. with updates and selects, i would expect that the time of finding the record(s) (to update or select) (the where-clause) depends on the size of the table and on whether indexes are used. Martin

[sqlite] Time scale on INSERT and UPDATE

Hello, does anyone have any experience in the amount of time increase for an UPDATE, INSERT, SELECT in relation to the size of the actual database? Is it proportional or exponential for example... Regards, Hannes

Re: [sqlite] Size of INSERT and UPDATE in TRANSACTION

Hello Hannes, I think no, you need not split your transaction. I do millions on insert in one transaction and it works real fast Martin Hannes Ricklefs schrieb: Hello, I was wondering if anyone has any experience with the number of INSERT UPDATE statements in one TRANSACTION. For example

Re: [sqlite] Are DELETE TRIGGERS recursive or not?

Hello [EMAIL PROTECTED], Thank you! I am very much looking forward to recursive delete triggers for just the very purpose you mentioned! Regards, Ralf >Not at this time. Though work is underway to change this. >We need recusive delete triggers in order to implement >cascadinig deletes for

[sqlite] Size of INSERT and UPDATE in TRANSACTION

Hello, I was wondering if anyone has any experience with the number of INSERT UPDATE statements in one TRANSACTION. For example I have the situation that i have to do around 20.000 INSERTS in one TRANSACTION, so I am wondering if it has any performance improvements if I split these up into

RE: [sqlite] Very Slow delete times on larger databases, please help!

Yes we found this out too. We never vacuum the file, it is acceptable for it to just get larger not smaller. We generate an indication on the current database capacity not from the file size but from the total number of pages in the database file minus the number of free pages in the database.