Asked  2 Years ago    Answers:  5   Viewed   436 times

I have a Doctrine entity with array type field:

 * @ORMTable()
class MyEntity

     * @var array $items
     * @ORMColumn( type="array" ) 
    private $items;

     * @param SomeItem $item 
    public function addItem(SomeItem $item)
        $this->items[] = $item;


If I add element to the array, this code works properly:

$myEntityObject->addItems(new SomeItem()); 

$myEntityObject is saved to the database with correct data (array is serialized, and deserialized when querying database).

Unfortunately, when I change one of the object inside array without changing size of that array, Doctrine does nothing if I'm trying to save changes to the database.

$items = $myEntityObject->getItems();

Although, print_r in the last line of that code displays changed object's data, Doctrine doesn't know that something was changed inside the array if array size didn't changed. Is there any way to force Doctrine to save changes made in that field (or gently inform it about changes in that field that needs to be saved) ?

Just found in documentation a way to solve my issue:

It requires a lot of changes in the code, but it works. Does someone know how to preserve default tracking policy for other fields and use NotifyPropertyChanged just for the field that stores array?



Doctrine uses identical operator (===) to compare changes between old and new values. The operator used on the same object (or array of objects) with different data always return true. There is the other way to solve this issue, you can clone an object that needs to be changed.

$items = $myEntityObject->getItems();
$items[0] = clone $items[0];

// ...

Or change the setItems() method (We need to clone only one object to persist the whole array)

public function setItems(array $items) 
    if (!empty($items) && $items === $this->items) {
        $items[key($items)] = clone current($items);
    $this->items = $items;

Regarding the second question:

Does someone know how to preserve default tracking policy for other fields and use NotifyPropertyChanged just for the field that stores array?

You cannot set tracking policy just for a one field.

Tuesday, August 16, 2022

It appears that whenever there is any error/exception encountered by the EntityManager in Doctrine, the connection is closed and the EntityManager is dead.

Since generally everything is wrapped in a transaction and that transaction is executed when $entityManager->flush() is called, you can try and catch the exception and attempt to re-excute or give up.

You may wish to examine the exact nature of the exception with more specific catch on the type, whether PDOException or something else.

For a MySQL has Gone Away exception, you can try to reconnect by resetting the EntityManager.

$managerRegistry = $this->getContainer()->get('doctrine');
$em = $managerRegistry->getEntityManager();

This should make the $em usable again. Note that you would have to re-persist everything again, since this $em is new.

Wednesday, October 5, 2022

As its bidirectional you need to update the association on both sides.

Add this function into the Category Entity (you can call it addChild if you like):

public function addProduct($product)

And then update both associations at the same time:

public function setProductCategory($product_category)
    $this->productCategory = $product_category;  

Tip: Dont use $children / $parent to describe Entities. Call it what it is $category / $product, you'll run into issues when you want to add in another "parent" relationship.

Sunday, December 4, 2022

Does some one have a clue how to force the current browsers to append the charset to the Content-Type header?

No, no browser has ever supplied a charset parameter with the application/x-www-form-urlencoded media type. What's more, the HTML spec which defines that type, does not propose a charset parameter, so the server can't reasonably expect to get one.

(HTML4 does expect a charset for the subparts of a multipart/form-data submission, but even in that case no browser actually complies.)


accept-charset is broken in IE, and shouldn't be used. It won't make a difference either way for forms in pages served as UTF-8, but in other cases it can end up with inconsistent results.

No, with forms you just have to serve the page they're in as UTF-8, and the results should come back as UTF-8 (with no identifying marks to tell you that (except potentially for the _charset_ hack, but Tomcat doesn't support that).

So you have to tell the Servlet container what encoding to use for parameters if you don't want it to fall back to its default (which is usually wrong). In a limited set of circumstances you may be able to call ServletRequest.setCharacterEncoding() to do this, but this tends to be brittle, and doesn't work at all for parameters taken from the query string. There's not a standardised Servlet-level fix for this, sadly. For Tomcat you usually have to muck about with the server.xml instead of being able to fix it in the app.

Wednesday, November 9, 2022

There is a package for what you want:

This plugin integrates the official Android APIs to perform in app updated that were released in 2019:

iOS does not offer such a functionality. You might want to look into e.g. If you call the methods above on a iOS device you'll run into a not-implemented exception.


Monday, August 8, 2022
Only authorized users can answer the search term. Please sign in first, or register a free account.
Not the answer you're looking for? Browse other questions tagged :

Browse Other Code Languages