Filtered value comparisons

Created on 14 April 2011, over 13 years ago
Updated 18 April 2024, 8 months ago

I can think of plenty of cases where the only significant characters in comparing two values are alphanumeric ones. Phone and credit card numbers, which can be embellished with optional brackets, dashes, and spaces, etc., are obvious examples.

Unfortunately MySQL (and I'm sure most other databases) don't have the regexp grunt to do those sorts of comparisons, so we will have to store our own converted values for any fields on which we want alphanumeric-only comparison, which will require our own table. This is overhead that has been so far avoided, but may help solve some other problems (eg. πŸ› Case sensitivity (uppercase and lowercase should not be considered unique) Closed: outdated ), so isn't a wholly bad thing.

Also I think leveraging Transliteration module will make this (and possibly other) functionality more locale-tolerant, so I don't think it's a problematic (possibly optional) dependency for this feature.

Hope to get a working patch posted shortly. If anybody wants to chip in sooner, let me know and I'll set up a public git repo. I need this feature for a D6 site, but happy to provide a D7 patch if the maintainer agrees to commit.

✨ Feature request
Status

Closed: outdated

Version

1.0

Component

Code

Created by

πŸ‡¦πŸ‡ΊAustralia Matthew Davidson

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡¦Ukraine AstonVictor

    I'm closing it because the issue was created a long time ago without any further steps.

    if you still need it then raise a new one.
    thanks

Production build 0.71.5 2024