Subject | Re: ASCII and ISO8859_1 |
---|---|
Author | zifnabbe |
Post date | 2004-05-02T14:04:56Z |
--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@t...>
wrote:
ISO8859_1 set and would be able to change the ASCII Column to
ISO8859_1 without a problem?
Or is it better to change the procedures and sql statements to use
CAST for the ASCII column?
Thanks
wrote:
> At 11:41 AM 2/05/2004 +0000, you wrote:set?
> >Hi,
> >
> >Is there a big difference between ASCII and ISO8859_1 character
> >now
> >My default is set to ISO8859_1, but I've one ASCII column and I'm
> >wondering if I might not just set this ASCII column to ISO8859_1I
> >
> >If I understand it correctly, if I keep using the ASCII table then
> >need to use CAST or the introducer formdifferent
>
> Yes, they are quite different. The ISO character sets use ANSI
> encoding. But as well as different encoding, they support
> characters, as well. US ASCII doesn't support accented characters,for
> example.Am I does correct to assume that the ASCII set is a subset in the
ISO8859_1 set and would be able to change the ASCII Column to
ISO8859_1 without a problem?
Or is it better to change the procedures and sql statements to use
CAST for the ASCII column?
Thanks
>
> /heLen