 |
 |
Archives of the TeradataForum
Message Posted: Wed, 04 Jan 2006 @ 16:05:52 GMT
| Subj: | | Re: Handling a 64 bit ID |
| |
| From: | | Dieter Noeth |
Christopher Coffing wrote:
| | We are trying to determine how to best handle a requirement to support a 64-bit ID in Teradata. | |
| | I just wanted to bounce something off of you to see if you concur. The project has a requirement for a 64-bit number as the ID for each of
the tables (A 32-bit value from a Source seed and a 32-bit value from another Source seed). This is my problem, Teradata doesn't support 64-bit
numbers and a double looses precision (I think 56-bits plus 8 for exponent in IEEE definition). | |
| | Is the only way to support this is to produce a two part key of two integers, then the external 64-bit client multiplies the numbers
together and reports the value to the User? | |
How about decimal(18,0), this is almost the range of a bigint (in fact it's a 64bit integer internally):
bigint: -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807
dec(18,0): -999,999,999,999,999,999 to 999,999,999,999,999,999
Dieter
| |
