From: | Michael Glaesemann <grzm(at)seespotcode(dot)net> |
---|---|
To: | gene(at)sotech(dot)us |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: datatype advice numeric vs. varchar |
Date: | 2007-01-18 06:22:24 |
Message-ID: | B4CFC8C3-ADFF-49E5-8963-59BE812B6777@seespotcode.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Jan 18, 2007, at 15:15 , Gene wrote:
> My calculations for disk space based off some information i found
> online are ( 8 + ( 2 bytes for every four digits) ) for numeric and (
> 4 + number of chars ) for a utf8 varchar datatype. Are these
> calculations still valid and has anyone tried using numeric for this
> purpose or is this really stupid?
While telephone numbers typically consist of digits, they're not
numbers: they're strings of digits. For example, a telephone number
in Tokyo is (typically) a string of 10 digits, beginning with "03".
0311111111 as numeric would have unexpected results when retrieved.
While you may not be concerned with Japanese phone numbers, I use it
as an example to show that telephone "numbers" are actually strings.
In short, use strings (text/varchar).
Michael Glaesemann
grzm seespotcode net
PS. The number of bytes used to represent characters in UTF-8 varies.
I believe digits (0-9) are all 1 byte/char.
From | Date | Subject | |
---|---|---|---|
Next Message | Gene | 2007-01-18 06:25:12 | Re: datatype advice numeric vs. varchar |
Previous Message | Martijn van Oosterhout | 2007-01-18 06:19:21 | Re: datatype advice numeric vs. varchar |