Is it hard to check?
On 12 Sty, 20:06, Parris wrote:
> Would that not cause namespace issues if there were more than one
> controller with the same name in the entire app? Doesn't the model
> need to be named PollPoll not just Poll?
>
> On Jan 12, 12:32 am, Grzegorz Pawlik wrote:
>
> > In 1.2 I
Would that not cause namespace issues if there were more than one
controller with the same name in the entire app? Doesn't the model
need to be named PollPoll not just Poll?
On Jan 12, 12:32 am, Grzegorz Pawlik wrote:
> In 1.2 I would name model Poll, and Tag, and in PollAppModel set
> $tablePref
In 1.2 I would name model Poll, and Tag, and in PollAppModel set
$tablePrefix = "poll_"
So You would have poll_polls, poll_tags and poll_posts_tags. As fas as
I remember - that worked :)
Btw, when You define relations It would be for Poll model
var $habtm = array("Poll.Tag");
Good luck
I'm not f
I posted this on stackoverflow, but didn't really get the response I
was looking for
Hi everyone,
I know naming conventions for tables used by plugins generally start
with the name of the plugin and then the model pluralized. For example
lets say I had a plugin called Poll, with a model also c
