[RFC] Require Timestampable model behavior only take one field

[SidRoberts]

Something that I found in phalcon/cphalcon#14027 is that the Timestampable model behavior has the option to pass a string or an array of fields:

https://github.com/phalcon/cphalcon/blob/7d8ffd16f6f44bf28d0d700b34cfd6121494023a/phalcon/Mvc/Model/Behavior/Timestampable.zep#L80

If you pass an array, those fields will be updated with the same timestamp and in the same format:

+-----+---------------------+---------------------+
| ID  | Timestamp1          | Timestamp2          |
|-----|---------------------|---------------------|
| 123 | 2019-05-04 08:55:23 | 2019-05-04 08:55:23 |
+-----+---------------------+---------------------+

Why would anyone need to legitimately use this? Is it safe to remove passing as an array?

[sergeyklay]

I could be wrong, but it seems @Jurigag can help us here.

[JABirchall]

Allows to automatically update a model’s attribute saving the datetime when a record is created or updated

So it should function the same as laravels timestamp attributes where created_at is set when the record is added and updated_at is changed when the record is updated. But it looks like all the datetime fields are updated to same time no matter what.

[SidRoberts]

Yeah, I think on creation, only createdAt should be altered. Technically, it hasn't been updated so updatedAt shouldn't have a value.

[niden]

I am fine with this being changed to only one field per model.