Re: User defined types -- Social Security number... - Mailing list pgsql-sql

From Michael Chaney
Subject Re: User defined types -- Social Security number...
Date
Msg-id 20040301211231.GA19105@michaelchaney.com
Whole thread Raw
In response to Re: User defined types -- Social Security number...  (Christopher Browne <cbbrowne@acm.org>)
List pgsql-sql
On Sun, Feb 29, 2004 at 11:11:31PM -0500, Christopher Browne wrote:
> The world rejoiced as mdchaney@michaelchaney.com (Michael Chaney) wrote:
> > Look, you're thinking way too hard on this.  An SSN is a 9-digit number,
> > nothing more.  There are some 9-digit numbers which aren't valid SSN's,
> > and you might want to get fancy and create a constraint for that.
> >
> > Regardless, you are making a *major* mistake of confusing data
> > storage with rendering.  It is common to *render* an SSN as
> > xxx-xx-xxxx and its cousin the FETID (Federal Employers Tax ID) as
> > xx-xxxxxxx.  To store the dashes makes no sense.  They're in the
> > same place each time, it's wasted data.
> >
> > Store the SSN as an "integer".  When you begin to think about this
> > correctly, the "leading zeros" problem disappears since that is also a
> > *rendering* issue.
> 
> Well put.
> 
> The one thing that is a bit unfortunate is that 32 bit ints aren't
> quite big enough for this.  You need 1 extra digit :-(.

For what?  The largest SSN is 999,999,999, a signed 32-bit int goes to
just over 2,000,000,000.  Ever hear of a "4GB limit"?

Michael
-- 
Michael Darrin Chaney
mdchaney@michaelchaney.com
http://www.michaelchaney.com/


pgsql-sql by date:

Previous
From: Joe Conway
Date:
Subject: Re: returning a recordset from PLpg/SQL
Next
From: Michael Chaney
Date:
Subject: Re: User defined types -- Social Security number...