X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type;
	bh=GswvFnhuswuLy+dt4iee0WNqGLGwHg4NFoPHpAgBC9Y=;
	b=H4FGZgQm4NuBjWiUjeo+IgFedH//QyYLsJ5L7OKVZFHs6G/huPAwfhsvxwjw2SNgon
	n6x5T0u5Ap1bVXGmdzORZMSEMp4tv1kvGn2oRq7wDazG0hnMyQ1JMMvBmjcADtzZfAsW
	SCLpSgHWKdQNEvHSiIGJXQIpBQhhg7FQ9OOId4jmLv/Ibx2hMHO9/FX9xOXB01TNiUGN
	GcNEALmuLZ9UzEtEXRTwukjJl1T1+W3rAiVxHvwBHLcbEWcTMCngvQYPDgyfEbSrWWB4
	Dn+XiSRR7UFHAoqru9No8rpBfT3llkxs1/Gv5PMi2GFyKdIgzYR5dwAiDKsEYV006iGA
	GOCA==
MIME-Version:	1.0
X-Received:	by 10.180.89.101 with SMTP id bn5mr17538733wib.20.1442166926064;
	Sun, 13 Sep 2015 10:55:26 -0700 (PDT)
In-Reply-To:	<20150913190132.1926c471@jive.levalinux.org>
References:	<20150913140631 DOT 1da1b78d AT jive DOT levalinux DOT org>
	<CAC4O8c_WSck-z2V+iQRZY5HJf2WOu6=ozRpmo6zFGUf5r6DjMA AT mail DOT gmail DOT com>
	<20150913190132 DOT 1926c471 AT jive DOT levalinux DOT org>
Date:	Sun, 13 Sep 2015 09:55:25 -0800
Message-ID:	<CAC4O8c-99=qdVrz_-sOLAcr+JGemWf3Gp1NoZzsthG-i8F7vNQ@mail.gmail.com>
Subject:	Re: [geda-user] Apollon
From:	"Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
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

On Sun, Sep 13, 2015 at 9:01 AM, Lev (leventelist AT gmail DOT com) [via
geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
> On Sun, 13 Sep 2015 08:43:01 -0800
> "Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]"
> <geda-user AT delorie DOT com> wrote:
>
>> I suggest putting it in the file as something human-readable.  It's an
>> easy translate to SQL.  SQL is unlikely to be a popular choice for
>> people who don't already use it, and all you get for it is a little
>> more speed from the parser.  I think there are lots of users who just
>> want to e.g. change a selected "R1" to "S1/R1" (that's how I started
>> anyway) and they are unlikely to want to fire up an SQL interface to
>> do it.  Why make them?
>
> Instead of fire up gvim, you fire up sqlitebrowser.
>
> One of my goal is to avoid manual file hacking.
>
> But you still can do it if you like.
>
> A script still can manipulate the file.

Obviously i'ts possible, the question is how hard is it for the
majority of users.  If you look at DBI.pm I think you cannot honestly
say that the example I give above will be easier via SQL than it is
now.

> I don't think xml/yaml is a better choice. They get very, very ugly. I

True, but so does SQL once things get complicated.  As it happens I've
done a lot of SQL so you can't fool me here :)

> don't see any reason why not use SQLite.

Because many, possibly most people aren't familiar with it.  Give
yourself credit for what you've learned about SQL, and acknowledge
that it isn't going to be instantaneous for others to get that
knowledge.

There are actually only two reason *to* use SQL.  One is parse speed,
which is not significant for most use cases.
The other is the additional work for you (or someone) to put it in a
readable format.  But its easy work and I hereby
volunteer to do it.

- Raw text -