Bug #26530

Unique-Constraint Errors are not handled by an ExtDirect Request

Added by Regine Rosewich over 10 years ago. Updated over 7 years ago.

Status:
On Hold
Priority:
Must have
Assignee:
-
Category:
ExtDirect
Target version:
-
Start date:
2011-05-01
Due date:
% Done:

0%

Estimated time:

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.

#1

Updated by Karsten Dambekalns about 10 years ago

  • Assignee deleted (Karsten Dambekalns)
#2

Updated by Karsten Dambekalns over 9 years ago

  • Category set to ExtDirect
#3

Updated by Karsten Dambekalns over 9 years ago

  • Status changed from New to On Hold

Without #30933 solved this cannot be done.

#4

Updated by Christian Müller over 7 years ago

  • Assignee set to Christian Müller
#5

Updated by Christian Müller over 7 years ago

  • Assignee deleted (Christian Müller)

Also available in: Atom PDF