Thanks, got the point :-)
On 11 apr, 13:08, "Dardo Sordi Bogado" <[EMAIL PROTECTED]> wrote:
> > Question: When would one deside to use ClassRegistry::init instead of
> > App:Import and new() ? Wouldn't that be more memory efficient?
>
> ClassRegistry::init() would store a reference, so it can b
> Question: When would one deside to use ClassRegistry::init instead of
> App:Import and new() ? Wouldn't that be more memory efficient?
ClassRegistry::init() would store a reference, so it can be reused
later and use App::import() internally. Use it if you plan reuse the
instance in other plac
Question: When would one deside to use ClassRegistry::init instead of
App:Import and new() ? Wouldn't that be more memory efficient?
On 11 apr, 01:59, "Dardo Sordi Bogado" <[EMAIL PROTECTED]> wrote:
> > I was wondering if it is possible to load models inside a controller
> > in the similar way
> I was wondering if it is possible to load models inside a controller
> in the similar way as codeigniter does, and if there is a way, how to
> do it
Yes, Well if you want to use more than one model in the same
controller, just tell cake so:
class FoosController extends AppController {
var
I was wondering if it is possible to load models inside a controller
in the similar way as codeigniter does, and if there is a way, how to
do it
It would be something like this
class Blog_controller extends Controller {
function blog()
{
$this->load->model('users_model',
