New attempt to get Model Serializer discussion going

In my VERY HUMBLE opinion, the way Phalcon serializes models should change.

Currently, only columns that map to physical database table fields are auto-serialized. This presents a huge problem for Caching algorithms that rely on model serialization. Essentially, once pulled back from the backend storage, your model will miss fields that are set in Model's post-fetch routine.

I propose that Phalcon serializes all properties defined in a model class that's inheriting from Phalcon\Mvc\Model.

It make sense because if this virtual columns could be defined in every methods in model it sould be traced on every request?
Better way is as i wrote, make any field in table, with any prefix you know for what you use it, describe it in database with comments and it will be clean.
I think that it is better clean solutions than an overloaded framework.

Temuri, i had the same problem, dependent on state of one field had to fill field which i want to serialize and find out that it is the best solution i could find that time. You, your team, database designer etc will know that this field exist, is for something (table field comments), without going to definition of your model.