[BUG]: Saving related entity in Phalcon 5

[slechtic]

Discussed in #16203

^{Originally posted by slechtic November 11, 2022}
Hi,

I'm trying to migrate from Phalcon v3 to v5 but I have a problem with updating related entity.

I have an entity Document and this entity has related entity DocumentHistory.

On Document entity there is hasMany relationship defined:

$this->hasMany('id', DocumentHistory::class, 'idDocument', ['alias' => 'documentHistories']);

DocumentHistory entity has belongsTo relationship:

$this->belongsTo('idDocument', Document::class, 'id',['alias' => 'document']);

when I create new DocumentHistory entity and assign existing Document entity, change some values on this entity (Document) and save DocumentHistory entity, only DocumentHistory is saved (created). Document entity is not updated but foreign key is set on DocumentHistory entity correctly. In case when both entities exist it works correctly.

$documentHistory = new DocumentHistory();

$document = Document::findFirst($id);
$document->setNumber($number);

$documentHistory->setDocument($document);
$documentHistory->save();

On DocumentHistory there is a setter:

public function setDocument(Document $document) {
    $this->document = $document;
}

This works for Phalcon v3. This will not be supported in v5 or it is a bug? Thank you.

My environent:

PHP 8.1.
Phalcon 5.1.0.
Postgresql 11

[slechtic]

Hi guys, did you have any chance to check this problem? We need to know whether it is a bug or expected behavior so that we can proceed with Phalcon 5 upgrade.

[Jeckerson]

Did you tried to migrate to v4 first?

[slechtic]

Did you tried to migrate to v4 first?

Yes I did. But there was a problem with segmentation fault and suggestion was migrate to v5. #16028

[slechtic]

Here you can test it https://github.com/slechtic/phalcon5_relationships

[markofo]

Hi @Jeckerson
could you please let us know whether this is expected behavior, bug, or we are using it wrong?

In the previous post from @slechtic, there is a docker image with the example of the issue where you can easily test it.

Is there someone from Phalcon team who can help us even as a paid consultation on this matter?

Thank you in advance!

Marek

[slechtic]

Hi @Jeckerson, any progress? Did you try to run my example project which I attached?

[GeoffreyCZ]

Hi @Jeckerson,

I have encountered the same issue as the OP. Could you give us an information whether it is a bug or not? I need to decide if I need to migrate my project to another FW.

[MartinZubek]

Hi, I've run into the same issue while migrating a project to newer Phalcon.

Šlechtič's docker image (from the link above) clearly illustrates the issue I have.

Can you please check it and tell us what went wrong?
Thanks in advance

[FPEPOSHI]

Hi @Jeckerson, same here. We are stuck with the upgrade of our current version to v5.

[Jeckerson]

I'll investigate.

[FPEPOSHI]

Hi @Jeckerson, do we have any update about the issue reported?