Skip to content

Fix: compare number field values numerically in search - #1361

Open
Rom1-B wants to merge 1 commit into
11.0/bugfixesfrom
support_47696
Open

Rom1-B wants to merge 1 commit into
11.0/bugfixesfrom
support_47696

Conversation

@Rom1-B

@Rom1-B Rom1-B commented Nov 18, 2026

Copy link
Copy Markdown
Contributor

Checklist before requesting a review

Please delete options that are not relevant.

  • I have performed a self-review of my code.
  • I have added tests (when available) that prove my fix is effective or that my feature works.
  • I have updated the CHANGELOG with a short functional description of the fix or new feature.
  • This change requires a documentation update.

Description

  • It fixes !47696
  • Searching a number field with is / is not returned nothing for values of 1000 or more, because values were cast to DECIMAL(10,7) which caps them at 999.9999999.
  • <, >, <= and >= compared values as text, so < 2000 excluded 999 but included 12345.
  • is not and negated criteria excluded items whose block was never saved.
  • Values are now compared numerically without precision limit (1000 equals 1000.0, comma accepted as decimal separator), negated criteria include items without value, a non numeric searched value matches nothing instead of raising a SQL warning, and is 0 matches items without value like core does.
User Warning: MySQL query warnings:
Warnings:
1264: Out of range value for column '(null)' at row 4
1264: Out of range value for column '(null)' at row 5

Screenshots (if appropriate):

@Rom1-B
Rom1-B requested review from a team, Herafia, Mary-Clb and jdurand-teclib and removed request for a team November 18, 2026 10:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant