'modified'=> array('type' => 'datetime', 'null' => '1',
> 'default' =>
> '', 'length' => null)
>);
> }
>
> but every page view always brings up first the auth tables (aros,
>
pe' => 'datetime', 'null' => '1',
'default' =>
'', 'length' => null)
);
}
but every page view always brings up first the auth tables (aros,
acos, aros_acos) and then every table that I use in the controller
even if the
As far as I know, the describe should not occur if there is is a
schema defined for the database tables. The new console in 1.2 should
generate this automatically when you create a new model with 'cake
bake'. I haven't tried it yet cause i can't find those bloody minutes
but i can't postpone it mu
SHOW PROCESSLIST
On 12/14/07, Grant Cox <[EMAIL PROTECTED]> wrote:
>
>
> How are you checking that you are getting a lot of DESCRIBE queries
> with DEBUG set to 0?
>
>
> On Dec 14, 7:09 am, "Olexandr Melnyk" <[EMAIL PROTECTED]> wrote:
> > Hello bakers,
> >
> > in one of applications I'm working on
How are you checking that you are getting a lot of DESCRIBE queries
with DEBUG set to 0?
On Dec 14, 7:09 am, "Olexandr Melnyk" <[EMAIL PROTECTED]> wrote:
> Hello bakers,
>
> in one of applications I'm working on, I have noticed DESCRIBE queries being
> executed on every page for all used models.
Hello bakers,
in one of applications I'm working on, I have noticed DESCRIBE queries being
executed on every page for all used models. With a load of page views, this
only creates problems.
As far as I know, such queries should be cached if
application is in production (DEBUG = 0), but I still ge