Great question, but of course, there is no “one true way”. As per @BenV, Magento does use the EAV model. My experience with it has been overwhelmingly positive, however it does trip up other users. Some considerations: 1. Performance. EAV requires complex, multi-table joins to populate your object with the relevant attributes. That does incur … Read more
The Doctrine team is not willing to implement this feature. There are several solutions to your problem, each having its own drawbacks: Add a custom numeric function: see this DQL RAND() function (might be slow if you have lots of matching rows) Use a native query (I personally try to avoid this solution, which I … Read more
The easiest way to do that is by binding the array itself as a parameter: $queryBuilder->andWhere(‘r.winner IN (:ids)’) ->setParameter(‘ids’, $ids);
You have to implement a __clone() method in your entities that sets the id to null and clones the relations if desired. Because if you keep the id in the related object it assumes that your new entity A has a relation to the existing entities B and C. Clone-method for A: public function __clone() … Read more
Using different object managers (entity managers) doesn’t allow the object graphs to intersect. That case is too complex and isn’t managed by Doctrine ORM. If you need such a case, keep the object graphs disconnected by saving the identifiers of the related objects (old style) instead of a reference to them, then manually get the … Read more
It is not a good idea to allow an entity object to rely on the entity manager. It ties the entity to the persistence layer, which was a problem Doctrine 2 was specifically trying to solve. The biggest hassle in relying on the entity manager is that it makes your model hard to test in … Read more
With php5.4 now you can do : use JsonSerializable; /** * @Entity(repositoryClass=”App\Entity\User”) * @Table(name=”user”) */ class MyUserEntity implements JsonSerializable { /** @Column(length=50) */ private $name; /** @Column(length=50) */ private $login; public function jsonSerialize() { return array( ‘name’ => $this->name, ‘login’=> $this->login, ); } } And then call json_encode(MyUserEntity);
Your Category entity is the inverse side of the relationship. Try changing addItems to look like this: public function addItem(\Ako\StoreBundle\Entity\Item $item) { $item->addCategory($this); $this->items[] = $item; } Note that I changed your plural names to singular, since you’re dealing with single entities, not collections.
Do you know now what are the ‘important’ function to add to be able to upload the photo and rename it? See the official documentation on how to do this. There are good working examples for a simple file upload. Also check the doctrine documentation for lifecycle callbacks. How do you check the extension to … Read more
A Many-To-Many association with additional values is not a Many-To-Many, but is indeed a new entity, since it now has an identifier (the two relations to the connected entities) and values. That’s also the reason why Many-To-Many associations are so rare: you tend to store additional properties in them, such as sorting, amount, etc. What … Read more