X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Message-ID: <20151224142825.23916.qmail@stuge.se> Date: Thu, 24 Dec 2015 15:28:25 +0100 From: "Peter Stuge (peter AT stuge DOT se) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Subject: Re: [geda-user] A fileformat library Mail-Followup-To: geda-user AT delorie DOT com References: <20151223194905 DOT 7676 DOT qmail AT stuge DOT se> <0AB5D926-731F-4A49-AA26-D06DAE7C2CB0 AT noqsi DOT com> <201512240626 DOT tBO6QuW0031998 AT envy DOT delorie DOT com> <20151224124303 DOT GA22838 AT cuci DOT nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151224124303.GA22838@cuci.nl> 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 Precedence: bulk Stephen R. van den Berg (srb AT cuci DOT nl) [via geda-user AT delorie DOT com] wrote: > When you then extend the structure in SQL which the exporter/importer > don't understand, you either live with the fact that you lose > information when you export/import it, or you extend the > exporter/importer as well to support the new structures. Or stay with the status quo, which I don't think is good enough. //Peter