Received: from exchange.bilgi.edu.tr (prol800.ibun.edu.tr [194.27.149.22]) by hub.org (8.9.3/8.9.3) with ESMTP id SAA38690 for ; Wed, 12 Apr 2000 18:26:11 -0400 (EDT) (envelope-from eroloz@bilgi.edu.tr) Received: from bilgi.edu.tr (194.27.149.13 [194.27.149.13]) by exchange.bilgi.edu.tr with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id HZ0S2RGW; Thu, 13 Apr 2000 03:22:47 +0300 Message-ID: <38F4F721.8F78C4C5@bilgi.edu.tr> Date: Thu, 13 Apr 2000 01:22:25 +0300 From: Erol Oz X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: "pgsql-sql@postgresql.org" Subject: Localization or an other solution Content-Type: text/plain; charset=iso-8859-9 Content-Transfer-Encoding: 8bit X-Archive-Number: 200004/130 Hi, As everybody knows, or at least guess, the Turkish-specific characters is ordered incorrectly unless you don't have localization support. (For example there is a letter like 's' but has a dot under it; this letter must come after 's'; without localization support this and other non-English ones come after 'z' ) According to the manual, localization causes the loose of performance. Beside, I scare to use localization which is not familiar to me. Because of these, I try to find an other solution. The one that I think on is - to use a seperate field for each of the fields that I want to order; - to put a correctly-sortable version of the data in the related field - and to use this extra fields for sorting purposes. Example: Original data: 'žimžek' In extra field: 'szzimszzek' Finally, my question is: In a table which has 100.000 or more records, which one will be more faster? Localization or this one. Thanks in advance Erol Oz