Re: Which field to use
- From: "Jamie Collins" <jamiecollins@xxxxxxxxxx>
- Date: 10 Nov 2006 02:21:51 -0800
On Nov 10, 5:25 am, "Allen Browne" <AllenBro...@xxxxxxxxxxxxxx> wrote:
I agree with your approach of using the 4 number fields.
It's atomic, and handles different types of domains sensibly.
So you would take a single atomic fact and split it into parts that
only have meaning when considered as a whole, for which you must
concatenate (generally an expensive operation) and change data type in
the process? Having to convert data every time your retrieve is always
a strong indication that your are storing it wrong.
Why not make it CHAR(15) and make the column/field Validation Rule
[0-9][0-9][0-9].[0-9][0-9][0-9].[0-9][0-9][0-9]
and probably some other rules beyond the basic pattern.
Jamie.
--
.
- Follow-Ups:
- Re: Which field to use
- From: Allen Browne
- Re: Which field to use
- References:
- Which field to use
- From: Ana_T
- Re: Which field to use
- From: Brendan Reynolds
- Re: Which field to use
- From: Allen Browne
- Which field to use
- Prev by Date: Re: one to one relationship help and database design question
- Next by Date: Re: Many-2-many relationships: Can I be told ...
- Previous by thread: Re: Which field to use
- Next by thread: Re: Which field to use
- Index(es):