Why not just join to the membership type table and sort on the type name? It would be much easier (and have much less overhead) and instantiating an array of objects and then creating a custom array sorting algorithm just to sort on this one value.
On 8/20/07, Justin Treher <[EMAIL PROTECTED]> wrote: > > My member class could be sorted in the database with no problem save for > one property. The membershipType property is an object. Therefore, if I want > to sort on membership type I'm dealing with trying to sort an array of > composed objects. Perhaps I need to ease up on the only use arrays of > objects in the view? I tell you that it seems very complicated to have an > entire object just for one lookup value (membershipType). > You are subscribed to cfcdev. To unsubscribe, please follow the instructions at http://www.cfczone.org/listserv.cfm CFCDev is supported by: Katapult Media, Inc. We are cool code geeks looking for fun projects to rock! www.katapultmedia.com An archive of the CFCDev list is available at www.mail-archive.com/cfcdev@cfczone.org
