On 25 abr, 08:36, Defranco <[EMAIL PROTECTED]> wrote:
> no answers? its so difficulty like that?
>
> /defranco
If you want to put routes in the database, thats one thing, and
googling around I'm sure you'll find some info wrt that.
If you want to access a controller before loading your routes, that's
a bit chicken and egg unless you instantiate everything manually. But
you shouldn't need a controller at all for what you are asking (even
if you make it work, you are potentially loading a lot of classes to
do that which you won't use) -just the model.
An obvious caveat: making your app dependent on the db to know what to
do even for pages that don't use the db is a fragile situation to put
yourself in. You'd be better of using the Configure class or otherwise
caching your db routes (forever) when you change them, and writing
some logic to look for the cached file or read from the Configure
class and add to the routes.
hth,
AD
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake
PHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---
