Not answering your question, but just FYI ... If this is data that's being retreived from a database, then my thinking would be to avoid xsl:sort completely if possible. I'd rather do sorting in the database using a SQL statement (SELECT ... ORDER BY ...) since it's probably better optimized for this.
Of course, if this isn't database data then please ignore me. :-) DR At 03:13 PM 11/16/01 -0600, you wrote: >Anyone know which is faster using Xalan (in Cocoon2)? <xsl:sort> for a >"number" type or a "text" type? > >Seems I remember reading that "string" compares take longer than numeric >ones as a rule. I have the option of sorting nodes based on either an >"employeeid" (integer) or "lastname" (text). > >While the project is new, I know the employeeids will not be more than 5 >digits. However, later they will. > >On the other hand, the lastnames could easily exceed 5 characters in length >or could overlap for two people at a location (i.e. Bob SMITH and Mike >SMITH). I will select the nodes by ID to ensure uniqueness, but when I uses >my <xsl:sort> command, I'd like it to use the "optimum" sort type. > >TIA! - Mark > > >--------------------------------------------------------------------- >Please check that your question has not already been answered in the >FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> > >To unsubscribe, e-mail: <[EMAIL PROTECTED]> >For additional commands, e-mail: <[EMAIL PROTECTED]> --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>