Personally I think that the change to find is one of the bigger improvements to 1.2. I could never remember the order of the many many arguments to find and had to look them up at least once a day. Putting them info an associative array helps me a lot because I don't have to remember "pointless" index-numbers. Not a very lofty reason but there it is.
The fate of findNeighbours et-al is, to me, a slightly different matter. That said. I see no harm in keeping the old methods as "wrappers" to the new ones... apart from confusing the api a bit I guess. /Martin On Feb 16, 3:50 pm, leo <[email protected]> wrote: > Maybe I'm being old fashioned, but I don't really see the sense in > deprecating functions like findAll and findNeighbours in favour of a > do-it-all-pseudo-overloaded find. The syntax of the find function I > now find extremely confusing e.g. possible parameters 'field' & > 'fields'. Made more so because the documentation is uncomprehensive > and unclear. Different operations require different parameters and as > these aren't well documented e.g. find('neighbors') I have to go to > the doc for the deprecated function and try to reinterpret what is > required. > > One of the great things about CakePHP is the way it simplifies PHP > operations e.g. the findAllBy magic function. Would there be any harm > in undeprecating functions like findAll and findNeighbours so that > their future is not in doubt? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
