Sorry there is an error I use print_r instead of pr because the debug
is set on 0
On 30 Mag, 09:28, "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> wrote:
> Only one thing : A gentleman.
> I a person use a forum It's for learn and not to say that your
> framework is a crap.
> If I use Cakephp maybe it's because I think that is light-years ahead
> of other frameworks.
> I post my code so you can see if I use good coding practices.
>
> class User extends AppModel
> {
> var $useDbConfig = "myDb";
> var $name = 'User';
> var $useTable ="user";
>
> var $primaryKey ="username";
>
> var $hasAndBelongsToMany = array('Network' =>
>
> array('className' => 'Network',
> 'joinTable' => 'utente_gruppo',
> 'foreignKey' => 'username',
> 'associationForeignKey'=> 'gruppo_id',
>
> 'order' => 'gruppo_nome ASC'
> ));
>
> var $hasMany = array('Ente' =>array('className' => 'Ente',
> 'foreignKey' => '',
>
> 'finderQuery' => 'SELECT ........'
> ),
> 'Team' =>array('className' =>
> 'Team',
> 'foreignKey' => '',
>
> 'finderQuery' => 'SELECT .......'
> )
> );
>
> }
>
> class UserController extends AppController
> {
> var $name = 'User';
>
> var $uses=array('Ente','Network','User','Team');
>
> var $components = array('Auth');
>
> function index($username="")
> {
> $utente = $this->User->read('',$username);
>
> echo "<pre>";
> pr($utente);
> echo "</pre>";
>
> $this->set('utente',$utente);
> }
>
> }
>
> The view is empty.
>
> On 29 Mag, 23:13, "Chris Hartjes" <[EMAIL PROTECTED]> wrote:
>
>
>
> > On Thu, May 29, 2008 at 4:56 PM, [EMAIL PROTECTED]
>
> > <[EMAIL PROTECTED]> wrote:
>
> > > The problem is that it's the same even if debug is off .
> > > The difference is smaller but Cake 1.1 seems faster than Cake 1.2
>
> > Ah, you crazy kids and your concerns about the speed of Cake. Back in
> > my day, we looked at all factors of an application before we started
> > blaming the code, since the database would inevitably be the
> > bottleneck unless we had written really shitty code or were actually
> > doing computationally-intensive work.
>
> > I think the additional features of 1.2 are what make it worth
> > upgrading from 1.1, and I hate to burst anyone's ego but I doubt your
> > application will get so much traffic that any alleged speed decrease
> > from Cake 1.2 will make a difference. Good coding practices go a long
> > way towards ensuring application speed.
>
> > Performance testing and benchmarking is an art in itself and unless
> > you use tools specifically dedicated towards those ends (like Xdebug
> > or Apache Benchmark or Siege ) you are just making shit up.
>
> > Have I used these tools on Cake? No. Why? Because I don't care about
> > CakePHP's speed. For 99.999% of those who use CakePHP, it is
> > MTFEIYFTR (More Than Fast Enough If You Follow The Rules). For the
> > other .001%, either change your code or go with a non-Cake solution.
>
> > This is the "Twitter sucks because of Rails" fallacy. Twitter sucks
> > because they built a messaging system using tools for building a
> > content management system.
>
> > So, to get back to your initial question from the beginning of the thread:
>
> > Upgrade to 1.2 because it is light-years ahead of 1.1 in available features.
>
> > Now get off my lawn!
>
> > --
> > Chris Hartjes
> > Internet Loudmouth
> > Motto for 2008: "Moving from herding elephants to handling snakes..."
> > @TheKeyBoard:http://www.littlehart.net/atthekeyboard- Nascondi testo tra
> > virgolette -
>
> - Mostra testo tra virgolette -
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
