r:
>
> $this->ModelName->id = null;
> $this->ModelName->save(array('fieldName' => $fieldValue));
>
> for 1.2.x in ModelController:
>
> $this->ModelName->create(array('fieldName' => $fieldValue));
> $this->ModelName->save();
&g
I'm fairly new to Cake so I think I might be missing something but so
far I've found Cake very limited when interacting with data from
sources other than forms. Once I understood that a model, eg. User,
wasn't actually a User object but a representation of a db table, I
began to look for the funct
Have a look at the book "PHP 5 Objects, Patterns, and
Practice" (search on Amazon for details). A very popular book for
getting your head around OOP and Design Patterns in PHP.
Darren.
On May 22, 7:49 pm, rtanz <[EMAIL PROTECTED]> wrote:
> ok thanks alot guys
>
> On May 22, 4:30 am, "Nathan Garz
Nice work, grigri. I'm fairly new to Cake and I thought that this
would be such a common thing to do that it would form part of the core
functionality. After all, if you are going to pass an array to any non-
Cake-specific function - that is, to any external application or a non-
Cake-specific fun
I'm sure this is a newbie question but I've been unable find the
answer. If I run findAll on a simple table with no joins, I get an
array with an unnecessary middle level with the model name, eg.
Array ( [0] => Array ( [User] => Array ( [id] => 1 [username] => user1
[emailaddress] => [EMAIL PROTE
