place components quering property from a SQL database

Bug #1750180 reported by efa
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
KiCad
Expired
Wishlist
Unassigned

Bug Description

almost all EDA schematics support placing parts, querying properties from a SQL database.
At least Part Number, Value, PCB Footprint and Schematic symbol name, should be extracted from the DB, but property list should be configurable.
In this manner a company can have a managed database of parts (organized by project, or so), and schematics can be validated against "authorized" components lists.
OrCAD Capture, Mentor DXdesign, Altium, and so on support this feature.
We use MySQL as remote parts database, but any compliant SQL DB is OK.
RFE: Let KiCAD be professional.

efa (efa)
description: updated
Changed in kicad:
importance: Undecided → Wishlist
Revision history for this message
zakhar nasimov (thedocument) wrote :

Things to note, feature should

-import/export into Kicad database from standardized formats including CSV with initial row detailing field

-be rapidly searchable by component type, value or other field

-user can add additional fields to database

Should be a stand alone module such as pcb calculator or footprint editor.

Changed in kicad:
status: New → Opinion
Revision history for this message
efa (efa) wrote :

Wayne please put back the status to New, there are no opinions in the Description of this RFE, everything there is verifiable fact

Revision history for this message
Wayne Stambaugh (stambaughw) wrote :

@efa "Let KiCAD be professional" is an opinion. Relational databases do not make an EDA professional. The "Opinion" status in launchpad is defined as "Doesn't fit with the project, but can be discussed." Using a database to store symbols has been dismissed in the past by the development team as unnecessary overhead. Once Python support is implemented for the schematic editors, it will be fairly easy to implement your own database support but it's not something that KiCad is likely to provide. So given that I set the status to "Opinion", I'm willing to discuss the idea. Otherwise I would have set the status to "Wont Fix".

Revision history for this message
efa (efa) wrote :

OK thank you. Take care that already now the 'database' of components supplied by KiCAD is similar/bigger than other professional EDA libraries, and big enough to be fitted in a real DB.
Continue to keep the library of parts locally on designer HDD, and editable, can be really undesired when parts number become so high. Normally company prefer to keep validated parts (scheme symbol is right, not out of production, in preferred parts list, other policy) under control on external server. DB is a good choice, sure not the only one.

Revision history for this message
efa (efa) wrote :

if needed, I can describe how exactly work the placing of parts, synch of parts and validation of parts with OrCAD Capture+CIS with a DB

Revision history for this message
KiCad Janitor (kicad-janitor) wrote :

KiCad bug tracker has moved to Gitlab. Try searching for "lp:#1750180" on https://gitlab.com/kicad/code/kicad/-/issues

Changed in kicad:
status: Opinion → Expired
Revision history for this message
efa (efa) wrote :

seems impossible to find this issue on gitlab.
Going to the provided link: https://gitlab.com/kicad/code/kicad/-/issues
and type something like:
"lp:#1750180"
"#1750180"
"1750180"
always results in 0 results.

Can you please provide the direct link to the issue?

Revision history for this message
efa (efa) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.