Thanks, its a shift from what I'm used to... although I've had enough problems with muddying logic/presentation that I'm determined to change my ways.
I have another question and I'm not sure if it might be more suited to a fresh post. I've been really impressed with Zend_Search_Lucene and I can't wait to eliminate almost all of the strain on my mysql server caused by SQL searches. However there are certain things I do with the SQL searches that I'm not sure how to achieve with Zend_Search_Lucene. For example, if I search for items by name and I receive a result set back with information on each item including cost etc, I always provide functionality to sort by name/cost etc. If I were to use Zend_Search_Lucene and receive a result set back what would the best way to deal with this type of functionality? Would it come down to array manipulation again? I do a lot of array manipulation but I usually rely on SQL when dealing with a very large amount of data. Does the performance of array functions compare favourably to SQL? If there are a huge amount of search results is it not likely that my scripts will fail due to running out of memory? What would be the recommended approach? -- View this message in context: http://www.nabble.com/View-Logic-tf3845561s16154.html#a10892374 Sent from the Zend Framework mailing list archive at Nabble.com.
