> From: Brendan Miller [mailto:[EMAIL PROTECTED] > > Out of curiosity, what kind of performance implications do you think > any of this (or your DataMap idea) would incur--is it really that huge?
Well, my first thought was that the look up shouldn't occur in the processInValue method. This gets called for each element in the array which could be hundreds of times. IMHO, the "ideal" solution would be that once Criteria are being processed into SQL, there should be one lookup that converts the column info into a Column object. This would have to deal with "pseudo" columns (E.g. aliased or function items). This object would have a method to get the ColumnMap object if it's a "real" column. This object is what is passed to all the build methods instead of a plain String "column" object. This would limit the lookup overhead to once per each criteria. DukeCE Privacy Statement: Please be advised that this e-mail and any files transmitted with it are confidential communication or may otherwise be privileged or confidential and are intended solely for the individual or entity to whom they are addressed. If you are not the intended recipient you may not rely on the contents of this email or any attachments, and we ask that you please not read, copy or retransmit this communication, but reply to the sender and destroy the email, its contents, and all copies thereof immediately. Any unauthorized dissemination, distribution or copying of this communication is strictly prohibited. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
