From owner-freebsd-hackers@FreeBSD.ORG Sat May 12 03:32:34 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 23DCD16A404 for ; Sat, 12 May 2007 03:32:34 +0000 (UTC) (envelope-from ivoras@fer.hr) Received: from pinus.cc.fer.hr (pinus.cc.fer.hr [161.53.73.18]) by mx1.freebsd.org (Postfix) with ESMTP id 7471413C469 for ; Sat, 12 May 2007 03:32:33 +0000 (UTC) (envelope-from ivoras@fer.hr) Received: from [161.53.72.113] (lara.cc.fer.hr [161.53.72.113]) by pinus.cc.fer.hr (8.12.2/8.12.2) with ESMTP id l4B9s23f019644; Fri, 11 May 2007 11:54:03 +0200 (MEST) Message-ID: <46443AF0.2070006@fer.hr> Date: Fri, 11 May 2007 11:44:16 +0200 From: Ivan Voras User-Agent: Thunderbird 1.5.0.10 (X11/20060911) MIME-Version: 1.0 To: =?UTF-8?B?RGFnLUVybGluZyBTbcO4cmdyYXY=?= References: <200705102105.27271.blackdragon@highveldmail.co.za> <4643C7DB.6000408@elischer.org> <863b233dq4.fsf@dwp.des.no> In-Reply-To: <863b233dq4.fsf@dwp.des.no> X-Enigmail-Version: 0.94.2.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigCEAEF8B7D5341ACCA7BDCDFB" Cc: freebsd-hackers@freebsd.org Subject: Re: New FreeBSD package system (a.k.a. Daemon Package System (dps)) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 May 2007 03:32:34 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigCEAEF8B7D5341ACCA7BDCDFB Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Dag-Erling Sm=C3=B8rgrav wrote: > Ivan Voras writes: >> You can inspect s sqlite database with the provided utility. Unless th= e >> database gets corrupted (which it tries to avoid by respecting ACID), >=20 > ACID is not something a database "respects", it is a set of guarantees > that it provides to the application. Avoiding database corruption is > a necessary requirement for, rather than a consequence of, ACID. I'm thinking of ACID as a set of ideas / procedures, the consequence of=20 which is avoiding corruption. Of course, there's a "hierarchy of=20 reliability" - the db relies on the file system to meet the=20 requirements, the file system relies on the hardware, etc. but if the db = doesn't make use of those, it's all for nothing. > Perhaps you mean that SQLite tries to avoid database corruption by usin= g > locks, and either scatter-gather writes or copy-on-write, and flushing > the file between transactions, to ensure consistency? It uses locks, a journal file (for DML transactions), and flushes data=20 between transactions. More info at: http://www.sqlite.org/lockingv3.html --------------enigCEAEF8B7D5341ACCA7BDCDFB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGRDr3ldnAQVacBcgRAth4AKDvmRRXyUcDKXlAEwCV3UZpSQa4XACgwwAT bYQej+XTB2FSuR/wrlQJdBA= =RAts -----END PGP SIGNATURE----- --------------enigCEAEF8B7D5341ACCA7BDCDFB--