Describe the bug
I'm a bit unsure with this and assuming this is a KiCad bug but I want to get this assumption approved from Part-DB users (because they have all requirements to approve this). A perhaps present limitation of HTTP libs could also be the source of this. Who knows(?). 🙂
I'm evaluating Part-DB as replacement for the KiCad Database Library feature. As this is an atomic part use one important thing is that changes to local values/fields must be detected by the schematic ERC. This is not "firing" always. Investigating. Changes to (some?) fields in Part-DB will trigger the ERC. (Timestamp based or field by field compare?)
Updating symbols in KiCad loads the new values but bulk updating schematics is a bit risky - this should be detected, evaluated and done part by part. There is a diff dialog in KiCad.
With the Database Library this worked as intended (when I tested it 🤔). A local changed field (in the schematic) got detected. A meanwhile changed field in the DB got detected. This was live, no caching. Very secure not to export wrong/outdated data into a BOM.
To Reproduce
- Add a part from a Part-DB lib into a schematic.
- Prove that the ERC is clean.
- Change the part value or a field like MPN (which should be updated always in the lib source => Part-DB)
- Check the ERC again.
- ERC isn't complaining.
Expected behavior
ERC should complain about changes in every field which is imported from Part-DB.
Server Side
- Part-DB Version: Part-DB 2.15.0 (docker compose installation)
- PHP Version: PHP 8.4.24
- Database Server: MySQL 8.0.46
Desktop
- OS: Win11
- KiCad 10.0.5 (latest stable)
Describe the bug
I'm a bit unsure with this and assuming this is a KiCad bug but I want to get this assumption approved from Part-DB users (because they have all requirements to approve this). A perhaps present limitation of HTTP libs could also be the source of this. Who knows(?). 🙂
I'm evaluating Part-DB as replacement for the KiCad Database Library feature. As this is an atomic part use one important thing is that changes to local values/fields must be detected by the schematic ERC. This is not "firing" always. Investigating. Changes to (some?) fields in Part-DB will trigger the ERC. (Timestamp based or field by field compare?)
Updating symbols in KiCad loads the new values but bulk updating schematics is a bit risky - this should be detected, evaluated and done part by part. There is a diff dialog in KiCad.
With the Database Library this worked as intended (when I tested it 🤔). A local changed field (in the schematic) got detected. A meanwhile changed field in the DB got detected. This was live, no caching. Very secure not to export wrong/outdated data into a BOM.
To Reproduce
Expected behavior
ERC should complain about changes in every field which is imported from Part-DB.
Server Side
Desktop