[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: gEDA-user: Parts!



Levente wrote:
> DJ Delorie wrote:
>   
>> Just FYI, I was mostly asking about the database aspect, not the
>> storage aspect.  Both aspects are interesting to read about, of
>> course.
>>     
>
> You might know it... I have a database for my parts. There is a stock 
> table in it. So far, I don't use the stock table, because I buy 1000 
> resistors at one go. So something is in my database, I must have some of 
> it (somewhere). :-)
>
> http://logonex.eu/phpmyadmin/index.php
>
> user: guest
> no password
>
> Select the component database.
>
> Btw... I have so far more than 300 parts in it. The only pity with this 
> system, is that it doesn't have support of footprint variants. :-(
>   

Gosh, I think it almost does.  You have a footprint column in your 
device table, and it seems as though only one footprint would apply to a 
specific device--- an 0603 resistor is always going to use the 0603 
footprint.  So if you had resistors with other footprints, they'd be 
different entries in the table, right?

I don't think you are using your schema very effectively, however.  I 
think your description field should at most contain the word "resistor", 
since you are capturing things like footprint and value in other fields. 
And I think you need a separate column for footprint symbol file name, 
then drop the ".fp" from your footprint field and adopt a standard 
naming convention for footprints. Then you could do a query for 
"description=resistor and value=10R and footprint=SO14".

Yours is a sledgehammer system, but I like it.  I'm a tad jealous, in 
fact.  :)


b.g.

-- 
Bill Gatliff
bgat@xxxxxxxxxxxxxxx



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