From owner-freebsd-hackers@FreeBSD.ORG Fri May 11 17:34:39 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 400A216A403 for ; Fri, 11 May 2007 17:34:39 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: from mired.org (vpn.mired.org [66.92.153.74]) by mx1.freebsd.org (Postfix) with SMTP id D888B13C468 for ; Fri, 11 May 2007 17:34:38 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: (qmail 41897 invoked by uid 1001); 11 May 2007 17:34:07 -0000 Received: by bhuda.mired.org (tmda-sendmail, from uid 1001); Fri, 11 May 2007 13:34:07 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17988.43279.93248.608136@bhuda.mired.org> Date: Fri, 11 May 2007 13:34:07 -0400 To: jos@catnook.com In-Reply-To: <20070511165612.GA48097@lizzy.catnook.local> References: <200705102105.27271.blackdragon@highveldmail.co.za> <4643C7DB.6000408@elischer.org> <17988.35412.231093.411177@bhuda.mired.org> <20070511165612.GA48097@lizzy.catnook.local> X-Mailer: VM 7.19 under Emacs 21.3.1 X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.1.11 (Ladyburn) From: Mike Meyer Cc: freebsd-hackers@freebsd.org Subject: Re: SQL in the base system (Was: 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: Fri, 11 May 2007 17:34:39 -0000 In <20070511165612.GA48097@lizzy.catnook.local>, Jos Backus typed: > On Fri, May 11, 2007 at 11:23:00AM -0400, Mike Meyer wrote: > [snip] > > How robust is it - can a corrupt block fry the entire database? > > Dunno, but "Transactions are atomic, consistent, isolated, and durable (ACID) > even after system crashes and power failures.". So it appears to try hard to > minimize the chance of corruption. Right. This is a good thing. However, the db *will* become corrupt. A disk block will fail to read, whatever. The question is asking how much data will be lost outside the corrupt data block? > > How about portability - can I move the file to a completely > > different architecture and still get the data from it? > "Database files can be freely shared between machines with different byte > orders." That sounds like a "somewhat". The desired answer is "If the version of sqllite runs on a platform, all database files will work on it." That they felt the need to point out that they are byte order independent implies that other architectural issues may be a problem. Of course, it could be that nobody has asked the right people that question. > Also, the code is in the public domain. Wow. That's everylicensecompliant. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information.