From: Bruce Momjian <maillist@candle.pha.pa.us>
Message-Id: <199906100054.UAA14722@candle.pha.pa.us>
Subject: Re: [HACKERS] Postgres 6.5 beta2 and beta3 problem
In-Reply-To: <375EBAA0.D5DE4B2E@trust.ee> from Hannu Krosing at "Jun 9, 1999
	10:04:00 pm"
To: Hannu Krosing <hannu@trust.ee>
Date: Wed, 9 Jun 1999 20:54:38 -0400 (EDT)
CC: Oleg Bartunov <oleg@sai.msu.su>,
	ZEUGSWETTER Andreas IZ5 <Andreas.Zeugswetter@telecom.at>,
	"'hackers@postgresql.org'" <hackers@postgreSQL.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

> Oleg Bartunov wrote:
> > 
> > 
> > Thanks for explanations. It would be great if I could specify for specific
> > columns if it needs locale. For now I have to pay decreasing in speed
> > just to enable locale for the only column of one database !!!
> > I always dream to be able to specify on fly 'SET LOCALE to ON|OFF'
> > It's a bit separate problem, but probably more easy to implement.
> 
> Actually the locale should be part of field definition (like length and 
> precision currently are) with default of ascii. 
> 
> And also it may be probably safest to maintain our own locale defs (as
> Oracle 
> currently does)so that things don't break if somebody changes the system
> ones.

Added to TODO:

	* Allow LOCALE on a per-column basis, default to ASCII

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026