Feature #8596
closedadd isEmpty() to Query
0%
Description
FLOW3 has the isEmpty() constraint to check collections for being empty, that should be synchronized to Extbase.
Updated by Felix Oertel over 14 years ago
- Status changed from New to Accepted
- Assignee set to Felix Oertel
- Target version set to Extbase 1.3.0beta1
- Start date set to 2010-07-08
- Estimated time deleted (
1.00 h)
I'll take care of that ...
regards, foertel
PS: who estimated 1 hour for that? the changeset over in FLOW3 has >1.000 lines ;-)
Updated by Marc Bastian Heinrichs almost 14 years ago
What is the status here? Is there a chance to get this in version 1.3?
I missed this in my extension I currently implmement.
Updated by Felix Oertel almost 14 years ago
- Target version changed from Extbase 1.3.0beta1 to Extbase 1.3.0beta3
- Start date changed from 2010-07-08 to 2010-12-02
Hey,
good question. i did not come to that yet ... i will try to get some technical advice (tomorrow?) and work on that. can't promise anything though ...
if anyone else is interested in this, feel free to contact me via mail to allow smooth handing over
regards, foertel
Updated by Marc Bastian Heinrichs almost 14 years ago
- Priority changed from Must have to Should have
- Target version changed from Extbase 1.3.0beta3 to Extbase 1.3.0
Updated by Marc Bastian Heinrichs over 13 years ago
- Target version changed from Extbase 1.3.0 to Extbase 1.4
Updated by Felix Oertel over 13 years ago
- Assignee deleted (
Felix Oertel) - Start date deleted (
2010-12-02)
Updated by Marc Bastian Heinrichs over 13 years ago
The corresponding commit from FLOW3
[~TASK] FLOW3 (Persistence): When persisting NULL values are now recorded and collection (array, SplObjectStorage) properties are restored as NULL if they contained NULL, resolves #6520.
[~TASK] FLOW3 (Persistence): Equality comparison in a query now works correctly when comparing against NULL, relates to #8299.
[+API] FLOW3 (Persistence): Query::isEmpty() has been added and can check for empty collection properties, relates to #8299.
[~TASK] FLOW3 (Persistence): The like() constraint now can be used case-insensitive (like equals); constraints do stricter checks on property and operand types.
Updated by Sebastian Kurfuerst over 13 years ago
- Category set to Extbase: Generic Persistence
- Status changed from Accepted to New
- Priority changed from Should have to Must have
Updated by Alexander Schnitzler about 12 years ago
- Priority changed from Must have to Should have
- Target version changed from Extbase 1.4 to Extbase 6.1
Updated by Alexander Schnitzler almost 12 years ago
- Assignee set to Alexander Schnitzler
Updated by Robert Weißgraeber over 11 years ago
- Target version changed from Extbase 6.1 to Extbase 6.2
Updated by Alexander Schnitzler over 11 years ago
- Status changed from New to On Hold
- Assignee deleted (
Alexander Schnitzler)
Updated by Anja Leichsenring over 11 years ago
- Target version changed from Extbase 6.2 to Extbase 6.3
Updated by most wanted over 10 years ago
Anybody interested in working on this issue together at the T3DD14's coding night on friday? I have prepared an example extension (with various object relations) which should cover some/most/all of the involved scenarios.
Updated by Anja Leichsenring about 10 years ago
- Status changed from On Hold to New
Updated by Alexander Opitz about 10 years ago
- Project changed from 534 to TYPO3 Core
- Category changed from Extbase: Generic Persistence 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 Riccardo De Contardi over 7 years ago
- Target version changed from 8 LTS to 9.0