Project

General

Profile

Actions

Bug #59691

closed

repository->add must not update existing object

Added by Peter Niederlag almost 10 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Extbase
Target version:
-
Start date:
2014-06-20
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
Tags:
Complexity:
Is Regression:
Yes
Sprint Focus:

Description

The behaviour of the repository->add() method was changed by changes https://review.typo3.org/19992/ and https://review.typo3.org/20134

The repository->add method must not update/handle an existing object that already has in identity. For Updating existing object the repository->update() method must be used.

->add() should (again) throw a proper Exception for an invalid usage of using add() for an existing object.

Actions #1

Updated by Gerrit Code Review almost 10 years ago

  • Status changed from New to Under Review

Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/30909

Actions #2

Updated by Gerrit Code Review almost 10 years ago

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/30909

Actions #3

Updated by Mathias Brodala over 9 years ago

But this would basically require a clunky construct like this if all you care about is persisting an object, no matter if it is new or not:

if ($foo->_isNew()) {
  $this->fooRepository->add($foo);
} else {
  $this->fooRepository->update($foo);
}

Quite ugly if you ask me.

Also note that not even the Generic persistence manager in TYPO3 Flow cares about this. (I know that the Doctrine persistence manager does since #34527.)

Actions #4

Updated by Peter Niederlag over 9 years ago

I know it's not looking nice and I know I found it to be stupid some years ago myself. But ...

- first of all this was an unintentional side effect of some patches!
- it really sucks if you have a create/new style application, which is just intended to create fresh/new objects. Now you/developer must take care of securing your application so it can't be abused to modify arbitrary objects of the same type

I prefer ugly code over my data being open for unintentional manipulatation.

Until this get's cleaned I suggest everyone in create/new actions (that don't have any access check) to use something like:

if ((int)$myobject->getUid() > 1) throw new Exception("Error");
# somebody trìed to goof in an existing object
Actions #5

Updated by Helmut Hummel over 9 years ago

Hi!

Mathias Brodala wrote:

Also note that not even the Generic persistence manager in TYPO3 Flow cares about this.

Which is a bug

(I know that the Doctrine persistence manager does since #34527.)

.. which was only fixed in the Doctrine persistence manager

I agree with Peter, that the initial behavior (throwing an exception) should be restored.

Actions #6

Updated by Gerrit Code Review over 9 years ago

Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/30909

Actions #7

Updated by Gerrit Code Review almost 9 years ago

Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/30909

Actions #8

Updated by Gerrit Code Review almost 9 years ago

Patch set 5 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/30909

Actions #9

Updated by Gerrit Code Review over 8 years ago

Patch set 6 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/30909

Actions #10

Updated by Gerrit Code Review over 8 years ago

Patch set 7 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/30909

Actions #11

Updated by Gerrit Code Review over 8 years ago

Patch set 8 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/30909

Actions #12

Updated by Mathias Schreiber over 8 years ago

  • Target version deleted (next-patchlevel)
Actions #13

Updated by Anja Leichsenring over 7 years ago

  • Status changed from Under Review to New

can someone please verify this issue is still valid? I am under the impression it was solved meanwhile.

Actions #14

Updated by Christian Eßl over 4 years ago

  • Category set to Extbase
Actions #15

Updated by Benni Mack almost 4 years ago

  • Status changed from New to Closed

will close this one now, I haven't gotten feedback for three years in the issue and the review are not worked on. If somebody wants to pick this up, we can re-open the issue.

Actions

Also available in: Atom PDF