Skip to content

Conversation

@tbialcz
Copy link
Contributor

@tbialcz tbialcz commented Jul 29, 2025

🎫 Issue IBX-9060

Description:

This PR fixes an issue where passing both 'read' and 'unread' statuses to the notification search form
resulted in a SQL cardinality error due to use of '=' instead of 'IN'. The criterion handler now uses
expr()->in() and PARAM_INT_ARRAY to support filtering by multiple status values correctly.

@tbialcz tbialcz force-pushed the notification-status-criterion-in-operator branch from e9d25aa to 4b56fb3 Compare July 29, 2025 11:41
@tbialcz tbialcz changed the base branch from main to 4.6 July 29, 2025 11:41
@tbialcz tbialcz requested a review from a team July 29, 2025 11:43
@ezrobot ezrobot requested review from Steveb-p, ViniTou, adamwojs, alongosz, barw4, ciastektk, konradoboza, mikadamczyk and wiewiurdp and removed request for a team July 29, 2025 11:43
@sonarqubecloud
Copy link

@adamwojs adamwojs merged commit 1c05b96 into 4.6 Jul 30, 2025
16 checks passed
@adamwojs adamwojs deleted the notification-status-criterion-in-operator branch July 30, 2025 06:34
@alongosz
Copy link
Member

What scares me a bit is that there's no need to update any tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants