Do you really have a model named Warehousetorontomapleavenue, with a
table of warehousetorontomapleavenues?
Surely this should be a Warehouse model with a record for
TorontoMapleAvenue?
Check out the new CakePHP Questions site http://cakeqs.org and help others with
their CakePHP related question
I would rather put the descriptions in the comments, especially if you
only use it when reviewing the files.
# Hendry
On Sat, Apr 17, 2010 at 1:59 AM, Scott wrote:
> Some of my model and controller classes have very long, and therefore
> descriptive, names. The problem is that it's a real pain
On Apr 17, 12:05 am, Scott wrote:
> I don't see anything about aliases in the documentation. Routes is
> not the same as what I'm looking for. A route would make it easy to
> redirect the user, but I'm talking about the controller and model
> names used within the code itself. For example, I
I don't see anything about aliases in the documentation. Routes is
not the same as what I'm looking for. A route would make it easy to
redirect the user, but I'm talking about the controller and model
names used within the code itself. For example, I would like to have
the model "Warehousetoront
On Apr 16, 7:59 pm, Scott wrote:
> Some of my model and controller classes have very long, and therefore
> descriptive, names. The problem is that it's a real pain to use these
> when coding, but I want the names to be as descriptive as possible
> when reviewing the files.
>
> It would be reall
Some of my model and controller classes have very long, and therefore
descriptive, names. The problem is that it's a real pain to use these
when coding, but I want the names to be as descriptive as possible
when reviewing the files.
It would be really nice if we could define an alias that could b
