mirror of
https://github.com/qelectrotech/qelectrotech-source-mirror.git
synced 2026-09-27 12:34:14 +02:00
ispyisail
ccf545d30c
ElementQueryWidget::queryStr() reads FROM element_nomenclature_view, and that view already excludes flagged elements in its own WHERE clause (see createElementNomenclatureView() in projectdatabase.cpp). This widget then added a second condition on top: "exclude_from_bom IS NULL OR exclude_from_bom != '1'" -- but nothing anywhere ever writes the literal string "1" to this key (the only writer stores "true"/"false"), so the clause was true for every row that could possibly reach this point and did nothing. Confirmed dead three separate ways while reviewing qelectrotech#765: reading the value only ever comes back "true" or "false" (never "1"), an exclude_from_bom="1" element still appeared in --export-bom output on a test fixture, and the surrounding filter_ construction shows this AND'd clause cannot change the query's result set regardless of what filter_ already holds. Confirmed it a fourth way once already, by initially misreading this same clause as evidence the feature was broken -- it was reading the WHERE without the FROM three lines above, which is exactly the trap being removed here for the next reader. ElementQueryWidget backs the BOM export dialog and the diagram table properties widget; neither has a headless CLI equivalent, so this could not be verified end-to-end through --export-bom the way the case-insensitivity fix could. Verified instead: the file compiles clean, and a load/resave/--export-bom smoke test on examples/tremie_vibrante.qet shows no change in app behaviour (98 components, matching the pre-change baseline -- expected, since --export-bom does not go through this widget at all). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>