From owner-freebsd-hackers@FreeBSD.ORG Fri May 11 19:15:50 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 E531616A404 for ; Fri, 11 May 2007 19:15:50 +0000 (UTC) (envelope-from jos@catnook.com) Received: from lizzy.dyndns.org (209-204-188-132.dsl.static.sonic.net [209.204.188.132]) by mx1.freebsd.org (Postfix) with SMTP id 9868313C459 for ; Fri, 11 May 2007 19:15:50 +0000 (UTC) (envelope-from jos@catnook.com) Received: (qmail 50448 invoked by uid 1000); 11 May 2007 19:16:12 -0000 Date: Fri, 11 May 2007 12:16:12 -0700 From: Jos Backus To: freebsd-hackers@freebsd.org Message-ID: <20070511191612.GA50329@lizzy.catnook.local> Mail-Followup-To: freebsd-hackers@freebsd.org References: <200705102105.27271.blackdragon@highveldmail.co.za> <4643C7DB.6000408@elischer.org> <17988.35412.231093.411177@bhuda.mired.org> <20070511165612.GA48097@lizzy.catnook.local> <17988.43279.93248.608136@bhuda.mired.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17988.43279.93248.608136@bhuda.mired.org> User-Agent: Mutt/1.5.15 (2007-04-06) 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 Reply-To: jos@catnook.com 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 19:15:51 -0000 On Fri, May 11, 2007 at 01:34:07PM -0400, Mike Meyer wrote: > 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? It's a trade-off. Use SMART to monitor your disks, or whatever. Dealing with a gazillion different file formats is a PITA from an automation perspective. > > > 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. Probably. Why don't you? :-) > > Also, the code is in the public domain. > > Wow. That's everylicensecompliant. I sense some sarcasm. Would the GPL have been an improvement in the context of this discussion? -- Jos Backus jos at catnook.com