Try the Ad-hoc joins:-
http://bakery.cakephp.org/articles/view/quick-tip-doing-ad-hoc-joins-in-model-find
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php
tal, Robots.*, Users.username
> FROM
> (`robots_tags` INNER JOIN robots ON (robots_tags.robot_id =
> robots.id))
> INNER JOIN users ON robots.user_id=users.id
> WHERE tag_id IN (1,2,3)
> GROUP BY robot_id
> ORDER BY total DESC
> LIMIT 4
> >
>
>
--
View this mess
Robot HABTM Tag
User hasMany Robot
Robot belongsTo User
I want to get related robots based on his tags. More tags in common,
more related.
So, whats the way to put this query using $this->Robot->find(...) or
$this->Robot->RobotsTag->find(...)
SELECT count(tag_id) as total, Robots.*, Users.usern
I only have a few general things to share. You have probably at least
some of this in mind already but sometimes repetition is good :)
First. It doesn't sound at all like you HAVE TO use plugins for what
you describe. Plugins in cake can basically be two things. An optional
functionality (a fract
Well, the system that I thought required requestAction() was like
this:
I wanted to build a cms that's so complete you would only need to
create a new database and a new css-file to create a whole new
website.
Plugins are used as codeblocks. So if I have a page with some content
(an article or wha
It really depends on why you are creating your CMS, as that would have a
strong influence on your architecture. If you can provide more specific
questions, maybe we/i can help :)
To address your technical question, about plugins with requestAction -
again, that depends on your architecture. I've n
Ok, some people told me I didn't need to use requestAction as much as
I thought.
I'll try to build a cms with plugins by only using it's models and
elements..
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP"
I've tried to think of several ways to build a cms in cake.
But every system I could think of depended a lot on plugins.
One system might use several plugins with one page load and that would
be quite slow cause you needed to use requestAction() a lot. (In that
system plugins weren't like mini-app
ard to tell what you're doing.
> > However I think most people would recommend you should do more inside
> > your models. Components should just be to help out controllers with
> > requests.
>
> > On Oct 31, 9:41 pm, Skal Tura <[EMAIL PROTECTED]> wrote:
>
>
ll what you're doing.
> However I think most people would recommend you should do more inside
> your models. Components should just be to help out controllers with
> requests.
>
> On Oct 31, 9:41 pm, Skal Tura <[EMAIL PROTECTED]> wrote:
>
>
>
> > I am wonde
am wondering did i chose the Cake way of doing things with this, or
> atleast close :)
>
> We have multiple models, all of which access same set of tables
> handling massive amounts of data, searched using fulltext indexes.
> There's additions, searches, modifies etc. from 2 diff
I am wondering did i chose the Cake way of doing things with this, or
atleast close :)
We have multiple models, all of which access same set of tables
handling massive amounts of data, searched using fulltext indexes.
There's additions, searches, modifies etc. from 2 different models, a
Start here:
http://manual.cakephp.org/appendix/blog_tutorial
It'll give you a good feel for how to handle basic things like that in
Cake.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Cake
PHP" group.
To post t
Dear Bakers,
As I'm rather new to the Cake concept, I would be very grateful for
some simple rules of thumb or links, concerning the following issue:
When it comes to PHP programming, my usual practice is to set up some
divs, into which I "include()" content based on simple GET vars.
A common
14 matches
Mail list logo
