delorie.com/archives/browse.cgi | search |
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:16:24 +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: | geda-user AT delorie DOT com |
Subject: | Re: [geda-user] pcb file format |
Message-ID: | <20150827131624.GC8319@cuci.nl> |
References: | <20150824223846 DOT 0ba61ba7 AT jive DOT levalinux DOT org> |
<20150825022302 DOT 21819 DOT qmail AT stuge DOT se> | |
MIME-Version: | 1.0 |
In-Reply-To: | <20150825022302.21819.qmail@stuge.se> |
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 |
Peter Stuge (peter AT stuge DOT se) [via geda-user AT delorie DOT com] wrote: >Thanks for starting to do this. I do architect databases and for >edacore I would work hard to avoid an N:N table. They aren't great. >It's better to have explicit FKs between tables. I might have a >single table which includes columns for all types of objects, and I >would have a group table with a FK parent field refering to itself. But then you'd have to add/alter columns if you want to accomodate new object types. What's so bad about an N:N table? -- Stephen.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |