To replace generateList I use find('all', array('fields' =>
array('id', 'name')) and then a set::combine.
I find out that using find('list', ..) with 'fields' did not work as I
expect ..(I was experimented, maybe my mistakes).
Somehow I like the new way, "generateList" was retrieving ALL FIELDS
and doing the equivalent of set::combine after.
I do not know exactly, the impact of performances, but I always like
to retrieve only the needed fields.
On Jan 10, 10:31 pm, AD7six <[EMAIL PROTECTED]> wrote:
> On Jan 10, 10:26 pm, lordG <[EMAIL PROTECTED]> wrote:
>
> > Hey Guys,
>
> > One of the great features i liked about the generateList was that you
> > could make a list of data that the id was the key and the data was the
> > value... e.g. generateList(null, null, null, '{n}.Model.id', '{n}')
>
> > Why remove generateList, why not just leave it and give the option of
> > both? By the looks of the code, it does not look like it supports the
> > '{n}' idea.
>
> > G
>
> By the look of what code..? The set class hasn't gone anywhere.
>
> hth,
>
> AD
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake
PHP" 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
-~----------~----~----~----~------~----~------~--~---
