|
Title: Character set error Post by: Allegra on July 14, 2010, 04:39:08 pm Please help me in understanding this issue -
Am trying to load from a Production to Development table. One of the field structure is varying from Prod to Dev. Production table column - Code: MY_PROD_FIELD CHAR(8) CHARACTER SET GRAPHIC CASESPECIFIC Development table column - Code: MY_DEV_FIELD CHAR(8) CHARACTER SET LATIN CASESPECIFIC Can anyone differentiate between these two character sets. Title: Re: Character set error Post by: Whoever on July 15, 2010, 11:39:26 am If it's anything like SQL server, the character set "Graphic" is capable of storing multi-byte characters - which is needed for many non-european languages (many Asian languages for example). The Latin character set is capable of storing single-byte characters (eg. English). In a way, the "Graphic" character set is a superset of the "Latin" character set. "CaseSpecific" indicates whether or not the "case" matters in string comparisons. "asdf" = "ASDF" would evaluate to true, if "NOT CASESPECIFIC" But would evaluate to false, if "CASESPECIFIC" Title: Re: Character set error Post by: Allegra on July 20, 2010, 07:40:30 pm hmmm...! :( Unable to get through..!
Can you please elaborate why it errored in my case..! ::) Title: Re: Character set error Post by: Whoever on July 22, 2010, 10:38:12 am hmmm...! :( Unable to get through..! What I say below is generic and may not be true for Teradata at all.Can you please elaborate why it errored in my case..! ::) Graphic character set holds each character in multiple bytes - consider it the superset. Latin Character set holds each character in one byte - consider it a subset. Latin to Graphic conversion is usually implicit and transparent. But Graphic to Latin conversion will not happen implicitly and will error out in most cases. |