 | |
Need some help on Normalization
comp.databases.sybase comp.databases.sybase
 |
| | Thread Tools | Display Modes |
#11
 
| |||
| |||
|
Re: Need some help on Normalization -
10-14-2008
, 02:55 AM
|
In article <62ed393e-9794-4c4f-a34a-b0eca18ecf10 @i76g2000hsf.googlegroups.com>, techtechx... (AT) gmail (DOT) com says... D) Separate the phone number into separate fields. That has nothing to do with normalization, unless you are going to store numbers in a separate table, with the area code being a key field (which is going way overboard, IMO). Also not if you want to be able to handle different countries (because every country has their own style for writing a phone number), though you might want to store the country code as a separate field. |
the country code from the rest of the number, because we send messages
to people's cell phones using an SMS service provider. Their rules
mandate that we have to send them the country code in a separate
field.
Other than that, there are absolutely no consistent rules for
formatting a phone number, especially between different countries, and
very often even within the same country. I'm tempted to carry two
versions of the phone number, one with punctuation and formatting
stripped out. It would be easier to search, because you could do { and
phone like '%1234%' } and not worry about where or whether the person
put dashes or spaces or pluses or parentheses, etc. etc. etc.
:-)
#12
| |||
| |||
|
|
In article <62ed393e-9794-4c4f-a34a-b0eca18ecf10 @i76g2000hsf.googlegroups.com>, techtechx... (AT) gmail (DOT) com says... D) Separate the phone number into separate fields. That has nothing to do with normalization, unless you are going to store numbers in a separate table, with the area code being a key field (which is going way overboard, IMO). Also not if you want to be able to handle different countries (because every country has their own style for writing a phone number), though you might want to store the country code as a separate field. |
the country code from the rest of the number, because we send messages
to people's cell phones using an SMS service provider. Their rules
mandate that we have to send them the country code in a separate
field.
Other than that, there are absolutely no consistent rules for
formatting a phone number, especially between different countries, and
very often even within the same country. I'm tempted to carry two
versions of the phone number, one with punctuation and formatting
stripped out. It would be easier to search, because you could do { and
phone like '%1234%' } and not worry about where or whether the person
put dashes or spaces or pluses or parentheses, etc. etc. etc.
:-)
#13
| |||
| |||
|
|
In article <62ed393e-9794-4c4f-a34a-b0eca18ecf10 @i76g2000hsf.googlegroups.com>, techtechx... (AT) gmail (DOT) com says... D) Separate the phone number into separate fields. That has nothing to do with normalization, unless you are going to store numbers in a separate table, with the area code being a key field (which is going way overboard, IMO). Also not if you want to be able to handle different countries (because every country has their own style for writing a phone number), though you might want to store the country code as a separate field. |
the country code from the rest of the number, because we send messages
to people's cell phones using an SMS service provider. Their rules
mandate that we have to send them the country code in a separate
field.
Other than that, there are absolutely no consistent rules for
formatting a phone number, especially between different countries, and
very often even within the same country. I'm tempted to carry two
versions of the phone number, one with punctuation and formatting
stripped out. It would be easier to search, because you could do { and
phone like '%1234%' } and not worry about where or whether the person
put dashes or spaces or pluses or parentheses, etc. etc. etc.
:-)
#14
| |||
| |||
|
|
In article <62ed393e-9794-4c4f-a34a-b0eca18ecf10 @i76g2000hsf.googlegroups.com>, techtechx... (AT) gmail (DOT) com says... D) Separate the phone number into separate fields. That has nothing to do with normalization, unless you are going to store numbers in a separate table, with the area code being a key field (which is going way overboard, IMO). Also not if you want to be able to handle different countries (because every country has their own style for writing a phone number), though you might want to store the country code as a separate field. |
the country code from the rest of the number, because we send messages
to people's cell phones using an SMS service provider. Their rules
mandate that we have to send them the country code in a separate
field.
Other than that, there are absolutely no consistent rules for
formatting a phone number, especially between different countries, and
very often even within the same country. I'm tempted to carry two
versions of the phone number, one with punctuation and formatting
stripped out. It would be easier to search, because you could do { and
phone like '%1234%' } and not worry about where or whether the person
put dashes or spaces or pluses or parentheses, etc. etc. etc.
:-)
#15
| |||
| |||
|
|
In article <62ed393e-9794-4c4f-a34a-b0eca18ecf10 @i76g2000hsf.googlegroups.com>, techtechx... (AT) gmail (DOT) com says... D) Separate the phone number into separate fields. That has nothing to do with normalization, unless you are going to store numbers in a separate table, with the area code being a key field (which is going way overboard, IMO). Also not if you want to be able to handle different countries (because every country has their own style for writing a phone number), though you might want to store the country code as a separate field. |
the country code from the rest of the number, because we send messages
to people's cell phones using an SMS service provider. Their rules
mandate that we have to send them the country code in a separate
field.
Other than that, there are absolutely no consistent rules for
formatting a phone number, especially between different countries, and
very often even within the same country. I'm tempted to carry two
versions of the phone number, one with punctuation and formatting
stripped out. It would be easier to search, because you could do { and
phone like '%1234%' } and not worry about where or whether the person
put dashes or spaces or pluses or parentheses, etc. etc. etc.
:-)
#16
| |||
| |||
|
|
In article <62ed393e-9794-4c4f-a34a-b0eca18ecf10 @i76g2000hsf.googlegroups.com>, techtechx... (AT) gmail (DOT) com says... D) Separate the phone number into separate fields. That has nothing to do with normalization, unless you are going to store numbers in a separate table, with the area code being a key field (which is going way overboard, IMO). Also not if you want to be able to handle different countries (because every country has their own style for writing a phone number), though you might want to store the country code as a separate field. |
the country code from the rest of the number, because we send messages
to people's cell phones using an SMS service provider. Their rules
mandate that we have to send them the country code in a separate
field.
Other than that, there are absolutely no consistent rules for
formatting a phone number, especially between different countries, and
very often even within the same country. I'm tempted to carry two
versions of the phone number, one with punctuation and formatting
stripped out. It would be easier to search, because you could do { and
phone like '%1234%' } and not worry about where or whether the person
put dashes or spaces or pluses or parentheses, etc. etc. etc.
:-)
#17
| |||
| |||
|
|
In article <62ed393e-9794-4c4f-a34a-b0eca18ecf10 @i76g2000hsf.googlegroups.com>, techtechx... (AT) gmail (DOT) com says... D) Separate the phone number into separate fields. That has nothing to do with normalization, unless you are going to store numbers in a separate table, with the area code being a key field (which is going way overboard, IMO). Also not if you want to be able to handle different countries (because every country has their own style for writing a phone number), though you might want to store the country code as a separate field. |
the country code from the rest of the number, because we send messages
to people's cell phones using an SMS service provider. Their rules
mandate that we have to send them the country code in a separate
field.
Other than that, there are absolutely no consistent rules for
formatting a phone number, especially between different countries, and
very often even within the same country. I'm tempted to carry two
versions of the phone number, one with punctuation and formatting
stripped out. It would be easier to search, because you could do { and
phone like '%1234%' } and not worry about where or whether the person
put dashes or spaces or pluses or parentheses, etc. etc. etc.
:-)
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.