X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Date:	Thu, 27 Aug 2015 15:46:12 +0200
From:	"Stephen R. van den Berg (srb AT cuci DOT nl) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	"Stephen R. van den Berg (srb AT cuci DOT nl) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Subject:	Re: [geda-user] pcb file format
Message-ID:	<20150827134612.GD8319@cuci.nl>
References:	<20150824223846 DOT 0ba61ba7 AT jive DOT levalinux DOT org>
	<20150827123056 DOT GA8319 AT cuci DOT nl>
MIME-Version:	1.0
In-Reply-To:	<20150827123056.GA8319@cuci.nl>
User-Agent:	Mutt/1.5.21 (2010-09-15)
Reply-To:	geda-user AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-user AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

Stephen R. van den Berg (srb AT cuci DOT nl) [via geda-user AT delorie DOT com] wrote:
>Lev (leventelist AT gmail DOT com) [via geda-user AT delorie DOT com] wrote:
>But instead of doing it in sqlite, I'd suggest PostgreSQL instead because

Incidentally, I do not propose changing the fileformat to anything SQL-like.
I'd say there is room for any and all fileformats, old and new.  It's just
that by using a proper SQL internal representation, you are able to accomodate
imports and exports of nearly all imaginable fileformats without loss of
information.

I think that using human readable fileformats is preferred over an SQL format.
Which is not to say that an SQL dump is possible to copy database content,
but that's more of a dump than a fileformat.
-- 
Stephen.

- Raw text -