Not signed in (Sign In)
Welcome Guest!
Want to take part in these discussions? If you have an account, sign in now.
If you don't have an account, apply for one now.
    • CommentAuthorkseguin
    • CommentTimeJan 3rd 2008 edited
     
    Shouldn't Find and it's siblings be static? I've looked at a number of PHP frameworks, and they all seem to make, what I consider to be, this huge mistake. My background isn't in PHP, so maybe this is just a language constraint.

    Any insight?
    • CommentAuthorKaste
    • CommentTimeJan 3rd 2008
     

    it's a language constraint

    • CommentAuthorkseguin
    • CommentTimeJan 3rd 2008
     
    Is this because in the base static method (ActiveRecord::Find) you can't tell the actual calling type of the class?

    Reading on PHP 5.3's late static binding (http://ca.php.net/manual/en/language.oop5.late-static-bindings.php), I believe this might make the implementation possible by being able to resolve the actual calling type, ala: static::__CLASS__ or something.
    • CommentAuthorKaste
    • CommentTimeJan 3rd 2008
     

    we can't use future-features at present.

    because we have an ActiveRecord with super-mapping all around, the bigger issue is IMHO that the ActiveRecord-class tends to explode.

    (In the famous 'patterns'-book the ActiveRecord was a concrete class.)

Add your comments
    Username Password
  • Format comments as