Hello. I posted a similar question a while back and received a bunch of responses. It depends on how you plan to use the numbers. If you plan to use them in calculations, then storing them as INTs is best. Also, breaking a number into separate components makes sense if you plan to use these components as qualifiers in WHERE clauses. I decided to store my numbers as VARCHARS after considering these issues and to allow for maximum flexibility although this is an inefficient use of memory.
HTH Asad On Fri, 29 Jul 2005, Scott Purcell wrote: > Hello, > > I am waffling on how to handle a column of phone numbers. I am not sure what > is common practice on the database side. Talking to some co-workers, some > feel it would be fine to use a varchar and others think there should be 3 > integer columns in the database for each number? > > Anyone have advice or know of best-practice on this subject? > > > Thanks, > Scott > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
