Inserting into a ManyToMany

Hey Roman R.

Can you tell me what's actually your problem?

If you need to create multiple relationships to the same entity is totally possible. This example may help you getting an idea of how to do it: http://docs.doctrine-projec...

Cheers!

Product already have many to many relations with processes and problem in that the product entity may have process which may repeats two or more times

Hey Roman R.

I'm not sure to understand your problem. Could you give me a bit more of context?

My entity Product have
/**
* @ORM\ManyToMany(targetEntity="CoreBundle\Entity\PostPrintOperation", inversedBy="products")
* @ORM\JoinTable(name="product_postPrint")
*/
private $postPrint;

but in some products I need have 2 or more identical $postPrint and when I try to save it I have Duplicate entry error

So, you need to have the same object into the same collection? In other words, Product::$postPrints is a collection of "PostPrintOperation" and in that collection you need to store the same object twice or more?

Yes! ))) Exactly what I need)

Hey Roman R.

I'm not sure why you need to do something like that but as far as I know that's a unique constraint violation. Maybe if you tell me a bit more about your use case I may be able to help you figuring out a workaround

Cheers!

Product must have collection of operations and some operations may call as one and two or more times

In that case you could create a service class that is on charge of deciding how many times an operation should be executed instead of adding the same operation multiple times to the same product

Thank you! Can you explain how realize this logic. This class it's a service or doctrine entity? And how in this case point count of operations when adding it to product

Well, it depends on your business logic. What events have to occur so you would add the same operation to the product?
If the answer requires data that you won't have in a further request, then you will have to store that information as an extra field of your ManyToMany relationship
If you don't know how to do that, here is a nice video that can guide you through: https://knpuniversity.com/s...

Cheers!

Hey sebastian

Can you tell me if you have any error messages?
As I could see your metadata looks fine, but would be nice to double check it, because, you know is not that easy reading xml from a comment :p

When you have a OneToMany relation and you are about to add a new entity to it, is recommendable that you setup both sides, e.g.

// Usuario
public function addSolicitud(Solicitud $solicitud)
{
    $this->solicitudes[] = $solicitud;
    // the inverse side
    $solicitud->setUser($this);
}

So, I believe you have a problem in somewhere setting up your relationships between objects. Try to split your process into smaller functions so you can debug step by step and be sure that everything is getting wired up as expected

Cheers!

to contextualize i do divide into the smallest i can with many layers: controller/Service/DAO... the controller that ask a VO(virtual object) of the class
to be filled with buildFromJson (Json coming from the front end on a request),and it does it well, then i send that VO to the service, there i find the needed objects from another layer the DAO(data acces objects) of each related entity, from the front end i got "servicios" coming so i make a foreach with the same logic, a VO of the data coming in the respective iteration and then this VO turning itself into a entity of the respective class.

I think you already got that from the previous post jaja

so i worked everything to be well setted , don't think that i'm still losing some set or get, cause i have no errors such as property not defined,and the solicitud is getting filled with the right objects, at least thats what i see in the properties setted and var_dumped...inmediately befor calling to persist, i did that to show you what is being setted.

just first lines..

$solicitud->getIdUsuario();
Usuario
object(Usuario)#138 (15) {...

$solicitud->getIdDatofacturacion();
DatoFacturacion
object(DatoFacturacion)#199 (10) {...

$solicitud->getIdDireccion();
Direccion
object(Direccion)#181 (9) {...

$solicitud->getServicios();
object(Doctrine\Common\Collections\ArrayCollection)#188 (1) {
["elements":"Doctrine\Common\Collections\ArrayCollection":private]=>
array(1) {
[0]=>
object(Servicio)#224 (12) {
["codigo":"Servicio":private]=>
string(7) "7yasdfy" ...

in servicio entity it even has the category entity on its idCategoria, same for Direccion and Datofacturacion that knows its relation to the user.

so in th service im establishing the user in some point

$solicitud->setIdUsuario($usuario);

and to the other side

$usuario->addSolicitudes($solicitud);
$resp = $this->usuarioDAO->updateSerialize($usuario);

now im trying with merge...not persist, same, not resulting...when it return it spills NULL

found a problem in teh relation between categoria and servicio, for some reason when i var dump $categoria->getServicios it does brings the arrayCollection but empty, without the services related...trying to fix that

Hey sebastian

I can think in 3 options:
1) Something is resetting your collection at some point in the execution flow
2) You forget to actually add a service to the collection
3) For some reason your code that calls "$solicitud->addServicio()" is not being called

updating trouble status jaja:

"A new entity was found through the relationship 'Solicitud#servicios' that was not configured to cascade persist operations for entity: Servicio@00000000044008fd0000000000ad7488. To solve this issue: Either explicitly call EntityManager#persist() on this unknown entity or configure cascade persist this association in the mapping for example @ManyToOne(..,cascade={\"persist\"}). If you cannot find out which entity causes the problem implement

effectively , the entity Solicitud is a new one, cause im trying to create it, the data to create this new Solicitud is being sended from the front-end, with services that i already extracted from DB... i think im about to resolve it.

what do you think about this loop..., should i be asking for a find for each service, as i have the respective id?

foreach($solicitudServicioVO->listadoServicio as $servicioVO)
{
$categoria = $this->categoriaDAO->find($servicioVO->getCategoriaId());
//maybe change this next line
$servicio = $servicioVO->toEntity();
// for this next one?? ill try and tell you...
$servicio = $this->servicioDAO->find($servicioVO->getId());
$servicio->setIdCategoria($categoria);
$solicitud->getServicios();
$solicitud->addServicio($servicio);

}

as i show here, i have the service data inside the $servicioVO, maybe i can go to find it in the DB, on this same loop.

when im doing Solicitud-> addServicio($servicio), im adding one of this fron-end sended services,(servicio), that can construct themselves as object of the Servicio class, on a toEntity pattern function.

so, i understand that doctrine might be complaining cause it thinks that the services added to the arrayCollection are not the same that it already knows from its DB, even though im setting them with its respective ID, cause the error message directs me more to verify the service entity...than the new Solicitud one.

...i did resolved this way, im testing it now, and it works fine, so...if someone else falls into this pit, don't trust your own constructed objects jajaja, doctrine wants it their way, and you shall obey, do find or find by to get the right objects instead of building them, even if the data inside is the same, the persist function got confused, it´s better for this situation to use the direct queried db objects.

Hey sebastian

Yeah you are right, Doctrine's ORM is a bit selfish about how to fetch your objects from the DB, you can't add constructor arguments for example. Looking at your use case maybe you only need to use Doctrine's DQL and doing object's hydration by your own,
This course may give some good ideas: https://knpuniversity.com/s...

Cheers and thanks for sharing your solution!

Hey Michael,

Looks like you don't need member_id in your form at all, so just try to remove this field from form. Then before saving a new weight-data, set the proper user and member IDs, which, as you said, you can get. I think it's the easiest solution of your problem. Does it help you? The another one solution is to "inject" member ID into the form type, for example with a hidden field, but since member is an entity - you will need Data Transformer for it. However, you have to do more extra work with validation in this case, so try the first suggestion in the first place.

P.S. Hello to Switzerland! ;)

Cheers!

Hi Victor
Thanks a lot for your answers!! I didn't add the field member_id to the form, it's just there. When I have a look in the Debug-tool > Forms > Submitted Data, there is field id, member and weight. But in my form I just added weight.

Hm, probably I misunderstand you... you say you have a form type, which holds only one field, i.e. weight and that's it, but when you render this form - you'll get an extra field, i.e. member_id, right? Are you sure you don't extend any other form type except the AbstractType in you custom form type? Could you show me what type has your weight field?

Cheers!

Yes, the form holds only the field weight and I won't get and other field.. But I found the mistake(?).. in the entity of the weight-table I seted the field member_id to "@Assert\NotBlank()" (I think you showed this in the tutorials, because its the "linked" field to the table memeber) and because of this the form wasn't valid. Is this ok so?
I like Symfony and your tutorials so much!! Keep on going! :-)

Yo Michael,

Yes, it totally makes sense! Good research. Then we can easily fix it I think. When you create a form, pass the entity with assigned member ID to it as the 2nd argument, I mean something like this:

$user = $this->getUser();
$member = $user->getMember();

$weight = new Weight();
$weight->setMember($member);

$form = $this->createForm(WeightType::class, $weight);
// And only then validate your form
$form->handleRequest($request);
if ($form->isValid()) {
     // persist and flush it!
}

Let me know if it works.

Cheers!

It works perfect!! Thanks a lot!!

Hey Richard

You mean checking if the user is a scientist instead of checking if exists in the genusScientists collection?

Hey Johan,

Do you mean addGenusScientist() method on Genus entity here? I think it'll be better to check this rule in a controller, probably using Symfony validator with custom callback. But if we talk about Value Objects - I think it's fine to hold this business logic inside them.

Cheers!

Hey Sokphea!

Look's like you have some extra characters, try this:

AppBundle\Entity\User:
        avatarUri: <imageUrl(100, 100, 'abstract')>

Update:
Oh wait, look's like those characters are added by "Disquss"
Can you show me how your fixtures.yml and user class look's like ?

Cheers!

Hello Diego, here the the code and it should be correct since I just copy from project code
AppBundle\Entity\User:
user_{1..10}:
email: admin+<current()>@gmail.com
plainPassword: '123456'
roles: ['ROLE_ADMIN']
avatarUri: <imageurl(100, 100,="" 'abstract')="">

Hey Chea,

First of all, you're missing comma before 'abstract' and have some extra chars from example, the correct example should be:

avatarUri: <imageUrl(100, 100, 'abstract')>

Also notice capitalized "U" in "imageUrl()".

I bet it should work now, but if not - please, double check that you have User::$avatarUri property and proper setter for it. You also can dump($this->avatarUri) inside its setter to see what value is assigned by Alice on loading fixtures.

Cheers!