> On Wed, 23 Jun 2004, Dennis Gearon wrote:
>
> > This is what has to be eventually done:(as sybase, and probably others do it)
> >
> > http://www.ianywhere.com/whitepapers/unicode.html
>
> Actually, what probably has to be eventually done is what's in the SQL
> spec.
>
> Which is AFAICS basically:
> Allow multiple encodings
> Allow multiple character sets (within an encoding)
Could Please explain more details for above. In my understanding a
character set can have multiple encodings but...
--
Tatsuo Ishii
> Allow one or more collations per character set
> Allow columns to specify character set and collation
> Allow literals in multiple character sets
> Allow translations and encoding conversions (as supported)
> Allow explicit COLLATE clauses to control ordering and comparisons.
> Handle identifiers in multiple character sets
>
> plus some misc things like allowing sets that control the default
> character set for literals for this session and such.
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
>
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
