Data Warehousing Community Forum
February 07, 2012, 07:32:22 am

Pages: [1]   Go Down
« previous next »
  Print  
Author Topic: Character set error  (Read 986 times)
Allegra
DW Apprentice
**

Reputation: +17/-0
Offline Offline

Posts: 75



View Profile
« 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.
Logged
@llegr@
what do you call an Ant with an AK47 ?
Whoever
Administrator
*****

Reputation: +34/-0
Offline Offline

Posts: 124



View Profile WWW
« Reply #1 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"
Logged
If most people said what’s on their minds, they’d be speechless.
Allegra
DW Apprentice
**

Reputation: +17/-0
Offline Offline

Posts: 75



View Profile
« Reply #2 on: July 20, 2010, 07:40:30 pm »
hmmm...!  Sad  Unable to get through..!

Can you please elaborate why it errored in my case..!  Roll Eyes
Logged
@llegr@
what do you call an Ant with an AK47 ?
Whoever
Administrator
*****

Reputation: +34/-0
Offline Offline

Posts: 124



View Profile WWW
« Reply #3 on: July 22, 2010, 10:38:12 am »
Quote from: Allegra on July 20, 2010, 07:40:30 pm
hmmm...!  Sad  Unable to get through..!

Can you please elaborate why it errored in my case..!  Roll Eyes
What I say below is generic and may not be true for Teradata at all.

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.
Logged
If most people said what’s on their minds, they’d be speechless.
Pages: [1]   Go Up
  Print  
« previous next »
 
Jump to: