• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: SQLite optimization
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: SQLite optimization


  • Subject: Re: SQLite optimization
  • From: Ruslan Zasukhin <email@hidden>
  • Date: Tue, 29 Aug 2006 16:02:59 +0300
  • Thread-topic: SQLite optimization

On 8/29/06 3:50 PM, "Aaron Burghardt" <email@hidden> wrote:

> You don't say whether you are querying the database or inserting
> data.  SQLite does not open the db file for each SQL statement, but
> when inserting data it creates a separate journal file for each
> transaction, so there is a fair amount of overhead per insert
> transaction.

Actually any dbms with transactions do this.

DB need to have for each transaction separate *logical* file. It can be
inside of some "virtual volume" but this not change main point.

--
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: SQLite optimization
      • From: Aaron Burghardt <email@hidden>
References: 
 >Re: SQLite optimization (From: Aaron Burghardt <email@hidden>)

  • Prev by Date: Re: SQLite optimization
  • Next by Date: Re: SQLite optimization
  • Previous by thread: Re: SQLite optimization
  • Next by thread: Re: SQLite optimization
  • Index(es):
    • Date
    • Thread