Re: gEDA-user: Parts DB (was: Re: Heavy Symbols and such)

[Peter Clifton <pcjc2@xxxxxxxxx>]

On Fri, 2007-12-14 at 20:39 -0800, Dave N6NZ wrote:

> partdesc is where my part number is defined, and is really the
> table that drives everything else.
> mysql> describe partdesc;
> +-----------+---------------+------+-----+---------+-------+
> | Field     | Type          | Null | Key | Default | Extra |
> +-----------+---------------+------+-----+---------+-------+
> | partnum   | varchar(20)   |      | PRI |         |       |
> | partdesc  | varchar(40)   |      |     |         |       |
> | value     | varchar(10)   | YES  |     | NULL    |       |
> | smt       | enum('N','Y') |      |     | N       |       |
> | package   | varchar(20)   | YES  |     | NULL    |       |
> | footprint | varchar(25)   | YES  |     | NULL    |       |
> | comment   | varchar(40)   | YES  |     | NULL    |       |
> +-----------+---------------+------+-----+---------+-------+
> 7 rows in set (0.00 sec)
> 
> 
> The assembly table allows me to have hierarchical part
> numbers for assemblies and sub-assemblies.  This is where
> I pull kit lists.  If refdes is non-NULL, qty is 1.  This
> allows the BOM to be stored in two different levels of
> detail.  In practice, any electronic parts tend to have
> a refdes, and things like #6 machine screws hove no refdes
> but have a count > 1.  An assembly part number can show up
> as a comppartnum of a higher level assembly allowing
> arbitrary hierarchy of sub-assemblies.

That is very cool.

One thing I thought of whilst reading this.. is that an "attributes"
table, to store attribute meta-data which will make it into gschem.
"SELECT * FROM attributes WHERE partnum = xxxxx;" might give you the
attribute results:

name      | value
----------+----------
refdes    | foo
value     | bar
model     | ......

etc..

I still see refdes as kindof special, but allowing this sort of table
will let you attach any useful netlistable attributes right into the
data-base.

I notice "symbol" is missing from your fields, and with this addition,
you might be able to place "parts" down directly in gschem if you
wanted.

Would you like A database GUI component chooser in gschem etc.. which
_only_ lets you pick from the database? I imagine this being available
as a "plugin" tab in the component selector, backed by a user-defined
application.

You could already do it with user-defined guile / script backed
component sources.

-- 
Peter Clifton

Electrical Engineering Division,
Engineering Department,
University of Cambridge,
9, JJ Thomson Avenue,
Cambridge
CB3 0FA

Tel: +44 (0)7729 980173 - (No signal in the lab!)



_______________________________________________
geda-user mailing list
geda-user@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user