See issue #3 for an example of how rows with an empty IPN are shown in KiCad, but does not produce useful behaviour and sometimes (but not always) causes KiCad to crash.
I am not sure what the best way to deal with this is. The problem is that the driver is implemented so that filtering can be done either using:
pk; or
IPN
When the initial SELECT * FROM "category" is issued, the driver doesn't know which is being used. This means if the driver always filters out rows without an IPN then the driver becomes unusable for people who set the key to pk, since if they don't use IPNs at all, then all the rows will get filtered. As an example, the InvenTree demo server does not always have IPNs attached to parts.
How to solve:
have an option that can be specified in the connection string to filter out empty IPNs
matmair
commented
1 year ago
See issue #3 for an example of how rows with an empty IPN are shown in KiCad, but does not produce useful behaviour and sometimes (but not always) causes KiCad to crash.
I am not sure what the best way to deal with this is. The problem is that the driver is implemented so that filtering can be done either using:
pk; orIPNWhen the initial
SELECT * FROM "category"is issued, the driver doesn't know which is being used. This means if the driver always filters out rows without anIPNthen the driver becomes unusable for people who set the key topk, since if they don't use IPNs at all, then all the rows will get filtered. As an example, the InvenTree demo server does not always have IPNs attached to parts.How to solve: