Re: beforeSave return false, what with afterFind...?!

2007-02-11 Thread Seb
If anybody is interested in that thread, solution 1 and 2 proposed by Nate don't work because merging two arrays recursively returns something like this; [code] Array ( [Article] = Array ( [id] = Array ( [0] = 1 [1]

Re: beforeSave return false, what with afterFind...?!

2007-01-21 Thread Seb
mmm... are ^^BUMPS^^ ok in google groups...?! ;) Seb. On Jan 8, 10:06 am, Seb [EMAIL PROTECTED] wrote: Hey Nate, Thanks for your time! What I'm trying to do evolves around virtual fields. For instance in the user model, the afterFind() method creates 2 virtual fields, one named name_lf

Re: beforeSave return false, what with afterFind...?!

2007-01-21 Thread nate
Sorry, didn't see you the first time. Okay, as I see it, there are 4 ways to solve your problem, 3 of which are basically variations on the same theme. The first three ways are these: // Controller: re-query your entire User model, and merge it with $this-data: $this-data =

Re: beforeSave return false, what with afterFind...?!

2007-01-07 Thread Seb
Hey Nate, Thanks for your time! What I'm trying to do evolves around virtual fields. For instance in the user model, the afterFind() method creates 2 virtual fields, one named name_lf and containing a user full name in 'lastname, firstname' format. This works like a charm. Now if I edit a

Re: beforeSave return false, what with afterFind...?!

2007-01-05 Thread nate
Ummm. beforeSave() and afterFind() are normally completely unrelated. It might help to post a code sample so we can see what it is that you're trying to do. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups

beforeSave return false, what with afterFind...?!

2007-01-04 Thread Seb
Hi guys... I'm not really having any problem but I found this one out this morning and it intrigues me... Question: In which case should a beforeSave() return false...? Context: I use afterFind() to create virtual fields ... and when the beforeSave() returns false, the afterFind is not called