4 ms·

Also, give me the ability to find nulls. Call it "other" or "unknown" if that's more accessible to normal people. In an ideal world, every product listing would

Also, give me the ability to find nulls. Call it "other" or "unknown" if that's more accessible to normal people. In an ideal world, every product listing would have all relevant fields populated (and with correct values). In the real world, practically all databases have errors. For example, my grocery store's soda category: https://www.heb.com/category/shop/beverages/soda/490015/490043 https://www.heb.com/category/shop/beverages/soda/490015/4900... There are 419 results. On the left, the Package filter has Bottle (168 results) and Can (139 results), which totals 307. All 419 products actually are bottles or cans, so 112 products just don't have the data. If you filter, they will be missing.

Phelinofist 3y ago
Access Denied Error 16 www.heb.com 2023-08-27 20:42:09 UTC What happened? This request was blocked by our security service Incident ID: 1309001730138387928-244354802817772362
emmanueloga_ 3y ago
Yes, yes and yes. When the filter for a given property is set to a value, but an specific item has a null for that property, the correct thing is to match the item (since it is unknown, it is wrong to assume the value doesn't match!). I would even prefer two result groups: matching filters and "maybe matching filters". But most faceted search engines just filter out items when properties may or may not match a property.