From owner-freebsd-hackers@FreeBSD.ORG Wed May 14 13:50:54 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6C2291065671; Wed, 14 May 2008 13:50:54 +0000 (UTC) (envelope-from lidl@rox.fddx.com) Received: from rox.fddx.com (rox.fddx.com [71.241.230.59]) by mx1.freebsd.org (Postfix) with ESMTP id 286A88FC14; Wed, 14 May 2008 13:50:53 +0000 (UTC) (envelope-from lidl@rox.fddx.com) Received: from rox.fddx.com (localhost.pix.net [127.0.0.1]) by rox.fddx.com (8.13.8+Sun/8.13.8) with ESMTP id m4EDorKS021798; Wed, 14 May 2008 09:50:53 -0400 (EDT) Received: (from lidl@localhost) by rox.fddx.com (8.13.8+Sun/8.13.8/Submit) id m4EDoqBw021797; Wed, 14 May 2008 09:50:52 -0400 (EDT) Date: Wed, 14 May 2008 09:50:52 -0400 From: "Kurt J. Lidl" To: Garrett Cooper Message-ID: <20080514135051.GA21370@pix.net> Mail-Followup-To: Garrett Cooper , James Mansion , freebsd-hackers@freebsd.org, Jeremy Chadwick , Anthony Pankov References: <9FC19AC2-DAD8-418C-8B9C-F129DEC58CEF@gmail.com> <15336578.20080512123806@mail.ru> <200805121153.00809.jonathan+freebsd-hackers@hst.org.za> <1663320218.20080512223531@mail.ru> <20080512152430.3720683e@mbook.local> <2117635718.20080513154406@mail.ru> <20080513121452.GA70860@eos.sc1.parodius.com> <20080513154137.GA28842@pix.net> <482A02CD.7040308@mansionfamily.plus.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.16 (2007-06-09) X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on rox.fddx.com X-Virus-Status: Clean Cc: freebsd-hackers@freebsd.org, Jeremy Chadwick , Anthony Pankov , James Mansion Subject: Re: BDB corrupt 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: Wed, 14 May 2008 13:50:54 -0000 On Wed, May 14, 2008 at 12:25:16AM -0700, Garrett Cooper wrote: > Most of the complaints about other DBs is licensing related, but SQLite's > complaint was also the fact that the past stability record was a bit rocky. One other thing to watch for in SQLite is the lack of atomicity in updates. It's not ACID, just like BDB 1.8x isn't ACID. Without a write-ahead log, you cannot be sure that the data written actually made it to stable storage, and as such, you cannot be sure that your database didn't get corrupted when the process stops in a non-optimal way. I view SQLite as adding syntactic sugar to your data access language. It doesn't give you real tranactions, it doesn't give you a write-ahead log, it doesn't give you referential integrity. Heck, the last time I looked (admitted, a while ago), it didn't even enforce column type checking on tables. (Put this string in the INT column? No problem!) -Kurt