Feature #46462
closedUniquenessValidator for models
0%
Description
I am currently writing a UniquenessValidator and I wanted to publish this here, maybe someone has an Idea about functionalities and features. I also want to check if such a validator would be welcome in the core or not. Simple thing: It checks if there is already a value for that column available, usable for e.g. login-names, email-addresses etc. My thoughts so far:
Basic validator:
/** * @validate Uniqueness */ protected $email;
Scoped checking, like: Each account can only have one user with that email-address, but the user can be there multiple times for different accounts.
/** * @validates Uniqueness(scope=user) */ protected $email;
Updated by Anja Leichsenring over 11 years ago
Flow has something similar, backport should be considered: https://forge.typo3.org/projects/package-typo3-flow3/repository/revisions/7ee3832c0769511f6804bafd9f770d4b6c1e322e
Updated by Alexander Schnitzler over 11 years ago
- Target version set to Extbase 6.2
Updated by Anja Leichsenring over 11 years ago
- Target version changed from Extbase 6.2 to Extbase 6.3
Updated by Alexander Opitz about 10 years ago
- Project changed from 534 to TYPO3 Core
- Category changed from Extbase: Validation to Extbase
- Target version changed from Extbase 6.3 to 7.0
Updated by Mathias Schreiber almost 10 years ago
- Target version changed from 7.0 to 7.1 (Cleanup)
Updated by Benni Mack over 9 years ago
- Target version changed from 7.1 (Cleanup) to 7.4 (Backend)
Updated by Susanne Moog over 9 years ago
- Target version changed from 7.4 (Backend) to 7.5
Updated by Benni Mack about 9 years ago
- Target version changed from 7.5 to 8 LTS
Updated by Benni Mack over 8 years ago
- Status changed from New to Needs Feedback
Pascal, care to implement that? Would be awesome!
Updated by Alexander Opitz about 8 years ago
- Status changed from Needs Feedback to New
Updated by Riccardo De Contardi over 7 years ago
- Target version changed from 8 LTS to 9.0
Updated by Christian Kuhn almost 3 years ago
- Status changed from New to Closed
Hey. I'm going to close this feature request for now: This issue is open since 10 years and nobody ever worked on it. It seems as if the pressure to have such an validator in the core isn't very high.
In case anyone wants to pick it up again, it can happen with an new issue.