What I understood from your original post was that you wanted to store the
users address in more than one model, i.e. the same data in multiple places, as
opposed to storing the data once in one place and creating references to it
from other places. Forgive me if I misunderstood.
Jeremy Burns
C
what do you mean with 'but it isn't storing the same data multiple
times' ?
On 15 Mrz., 05:49, Jeremy Burns | Class Outfit
wrote:
> Yes, this takes your data array and stores parts of it in different models,
> but it isn't storing the same data multiple times. That's an admin nightmare,
> so as
Yes, this takes your data array and stores parts of it in different models, but
it isn't storing the same data multiple times. That's an admin nightmare, so as
I mentioned before, the best solution is to examine your database design.
Jeremy Burns
Class Outfit
jeremybu...@classoutfit.com
http://
Design your database better so it's only stored once.
Jeremy Burns
Class Outfit
jeremybu...@classoutfit.com
http://www.classoutfit.com
On 14 Mar 2011, at 23:36, duderion wrote:
> hi guys,
>
> i have a users/add form, and i want to store the users address data to
> several models (adresses,acco
i found a cool solution :D
http://nuts-and-bolts-of-cakephp.com/2008/08/01/practical-use-of-saveall-part-1-working-with-multiple-models/
greets
duderion
On Mar 15, 12:36 am, duderion wrote:
> hi guys,
>
> i have a users/add form, and i want to store the users address data to
> several models (a
hi guys,
i have a users/add form, and i want to store the users address data to
several models (adresses,accounts, etc)
so i have more than one model to validate.
whats the best practice ?
duderion
--
Our newest site for the community: CakePHP Video Tutorials
http://tv.cakephp.org
Check out