Cricket, that was what you meant? http://teknoid.wordpress.com/2009/03/11/blacklist-your-model-fields-for-save/
If so, yeah, that would do it, with just a tweak on beforeSave. Good call. AD7six, I solved my problem by, alas, giving it up and writing everything on beforeSave. I'll check if it has been already ticketed and maybe write a patch to try and solve this problem. However, I think it's a MySQL issue. I don't have any idea if this discussion applies to other DBs like postgreSQL, Firebird, as I don't have much knowledge of these. On 17 jul, 12:26, AD7six <[email protected]> wrote: > On Jul 16, 6:08 pm, djogo <[email protected]> wrote: > > > yeah, it's so stupidly easy to do it in MySQL, it's a shame that I > > have to write any code at all in beforeSave() to accomplish the same > > thing. > > > RAPID DEVELOPMENT, they say. > > > Maybe the model could have a "no-mess-field-list", or fields that will > > be left alone when saving or updating. > > If you're writing any code at all to fix this issue it should be in a > test case and patch. Cake's goal is to not repeat code/process-logic > that includes not doing something in php which you're already doing/ > capable of doing in the DB layer (and it's just a consequence of > CURRENT_TIMESTAMP not being understood correctly). If you already > ticketed this please link to it from this thread. > > Cheers, > AD Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
