Bug #26530
Unique-Constraint Errors are not handled by an ExtDirect Request
| Status: | On Hold | Start date: | 2011-05-01 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | ExtDirect | |||
| Target version: | - | |||
| Votes: | 0 |
Description
Though it is possible to add unique-constraints to a table with the doctrine 2 ORM (and that works really fine), errors thrown when trying to add duplicate values to a unique-constraint property are not handled by an ExtDirect Request. (Such transactions give back "Succes: true").
Any errors of the doctrine 2 ORM should at least throw a "Success: false" in an ExtDirect-Request.
Related issues
| blocked by TYPO3.Flow - Feature #30933: Check for unique constraints on add() | Needs Feedback | 2011-10-14 |
History
Updated by Karsten Dambekalns over 1 year ago
- Assignee deleted (
Karsten Dambekalns)
Updated by Karsten Dambekalns 11 months ago
- Category set to ExtDirect
Updated by Karsten Dambekalns 11 months ago
- Status changed from New to On Hold
Without #30933 solved this cannot be done.