Modeling zip+4
From: dawn <dawnwolthuis_at_gmail.com>
Date: 13 Apr 2006 15:18:45 -0700
Message-ID: <1144966725.811878.133430_at_i39g2000cwa.googlegroups.com>
What is a "right way" to model (logical model) a postal code, including zip+4? Because the zip+4 was an add-on and is not always used for mailing or analytical purposes, I would think that attributes of postCode (char 6) and zip4 (char 4) might be typical. Would that be the best approach from a theory perspective? Are there either theory or practical advantages to making these either separate or combined attributes? Would it be better as a single char 10 (including -) or char 9 (excluding -) attribute where the first 5 are sometimes extracted for analysis of US data?
Date: 13 Apr 2006 15:18:45 -0700
Message-ID: <1144966725.811878.133430_at_i39g2000cwa.googlegroups.com>
What is a "right way" to model (logical model) a postal code, including zip+4? Because the zip+4 was an add-on and is not always used for mailing or analytical purposes, I would think that attributes of postCode (char 6) and zip4 (char 4) might be typical. Would that be the best approach from a theory perspective? Are there either theory or practical advantages to making these either separate or combined attributes? Would it be better as a single char 10 (including -) or char 9 (excluding -) attribute where the first 5 are sometimes extracted for analysis of US data?
Thanks. --dawn Received on Fri Apr 14 2006 - 00:18:45 CEST