Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 76675 invoked by uid 500); 16 Nov 2001 22:31:28 -0000 Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-users@xml.apache.org Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 76664 invoked from network); 16 Nov 2001 22:31:28 -0000 Message-Id: <4.3.1.1.20011116172418.00a77100@mail.dti.net> X-Sender: darose@mail.dti.net X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Fri, 16 Nov 2001 17:26:57 -0500 To: cocoon-users@xml.apache.org From: David Rosenstrauch Subject: Re: Xalan and xsl:sort speed by type In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N 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)? 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 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. > >To unsubscribe, e-mail: >For additional commands, e-mail: --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: