From: Erol Oz <eroloz@bilgi.edu.tr>
To: pgsql-sql@postgresql.org <pgsql-sql@postgresql.org>
Subject: Localization or an other solution
Date: Thu, 13 Apr 2000 01:22:25 +0300
Message-ID: <38F4F721.8F78C4C5@bilgi.edu.tr> (raw)
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: eroloz@bilgi.edu.tr
Subject: Re: Localization or an other solution
In-Reply-To: <38F4F721.8F78C4C5@bilgi.edu.tr>
References: <38F4F721.8F78C4C5@bilgi.edu.tr>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox