[symfony-users] Re: Timestampable

2010-08-01 Thread Richtermeister
You can override the isModified() method on the object to introduce that custom logic. Currently it returns whether any field has been modified. You can change it to return false if only the view field has been modified. Daniel On Jul 31, 6:13 pm, comb sa...@gmx.net wrote: Well I need the

[symfony-users] Re: Timestampable

2010-08-01 Thread pghoratiu
You can store the column in a separate table and link it to the master table 1:1 relationship. An even better solution is to store this in memcache (also use the memcache incrementation mechanism) and save this value in the database from time to time. gabriel On Jul 30, 11:18 am, comb

[symfony-users] Re: Timestampable

2010-07-31 Thread comb
Well I need the updated_at field if some other fields are updated. Only the views-field should not generate a change of the updated_at.. On Jul 30, 4:08 pm, Aldaron frala...@gmail.com wrote: If you don't need to auto update this field then you should not use timestampable.. Try to set the

[symfony-users] Re: Timestampable

2010-07-30 Thread Aldaron
If you don't need to auto update this field then you should not use timestampable.. Try to set the update_at field inside your update sentence to updated_at = $invoker-getUpdateAt() On 30 jul, 04:18, comb sa...@gmx.net wrote: Hi! I use the Timestampable behavior on a model. The model counts