Path: news.easynews.com!core-easynews!newsfeed1.easynews.com!easynews.com!easynews!priapus.visi.com!news-out.visi.com!petbe.visi.com!proxad.net!freenix!grolier!foorum!not-for-mail From: Philippe Newsgroups: comp.databases.oracle.server Subject: NLS_COMP and indexes Date: 06 Jun 2003 09:04:48 GMT Message-ID: <200366-10448-260412@foorum.com> NNTP-Posting-Host: 81.50.97.251 NNTP-Posting-Date: 06 Jun 2003 09:04:48 GMT X-Complaints-To: abuse@foorum.fr X-POSTER: foorum.com X-Foorum_user_tmp_id: 200366-10448-705548-81.50.97.251-club-internet X-Originating-User: 81.50.97.251 X-Newsreader: Foorum Lines: 16 Xref: core-easynews comp.databases.oracle.server:188828 X-Received-Date: Fri, 06 Jun 2003 01:12:09 MST (news.easynews.com) I'd like to force NLS_COMP to ANSI instead of default BINARY to have the same linguistic sort order in ORDER BY and WHERE clauses. (My NLS_SORT is 'French') Will this affect performances ? Will I have to rebuild indexes ? Indeed Oracle documentation specifies : >>As a final note, when NLS_COMP is set to ANSI, a linguistic index must exist on the column where the linguistic order is desired. To enable a linguistic index, use the syntax: SVRMGR> CREATE INDEX i ON t(NLSSORT(col, 'NLSSORT=FRENCH'));<< -- Ce message a ete poste via la plateforme Web club-Internet.fr This message has been posted by the Web platform club-Internet.fr http://forums.club-internet.fr/