Date: Fri, 11 May 2007 11:44:16 +0200 From: Ivan Voras <ivoras@fer.hr> To: =?UTF-8?B?RGFnLUVybGluZyBTbcO4cmdyYXY=?= <des@des.no> Cc: freebsd-hackers@freebsd.org Subject: Re: New FreeBSD package system (a.k.a. Daemon Package System (dps)) Message-ID: <46443AF0.2070006@fer.hr> In-Reply-To: <863b233dq4.fsf@dwp.des.no> References: <200705102105.27271.blackdragon@highveldmail.co.za> <f20c8u$htp$1@sea.gmane.org> <4643C7DB.6000408@elischer.org> <f219f6$3ls$1@sea.gmane.org> <863b233dq4.fsf@dwp.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <ivoras@fer.hr> 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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46443AF0.2070006>