Storage Box wrote:

> A bigint would be overkill since it is not a 64-bit value. So, a int/bigint
> field can legally store hexadecimal values?

OK had not read properly - saw 2 and 32bit integer, along with char(16)
Yes a simple INTEGER will do!

> Really what I wanted to know is how to store a 16-bit hexadecimal
> string/binary value. I wanted to be sure that a char(16) would be efficient
> enough to justify it (it's no integer but hey, it's more useful).

char(16) will store 16 characters. They could be restricted to 0-9,A-F
for hex, in which case THIS stores a 64 bit number. Thich is why I was
thinking BIGINT.

You need to think about what you are trying to do. The database will
store a 32 bit number in an INTEGER. How you display it is up to you,
you do not need to convert it hexadecimal before you store it !

--
Lester Caine
-----------------------------
L.S.Caine Electronic Services