Re: Call for an API standard for SQL statements

"Gene Wirchenko" <genew_at_mail.ocis.net> wrote in message news:h8ain01o4cai43jn0ggv8j9323hpjoubao_at_4ax.com...
> fredrik_bertilsson_at_passagen.se (Fredrik Bertilsson) wrote:
>
> >"Mikito Harakiri" <mikharakiri_at_iahu.com> wrote:
> >> What methods class TelephoneNo can possibly have?
> >getFormatted()
> >getCountryCode()
> >getAreaCode()

Would *all* users of the database have similar interpretation of those?

For example, user A prefers to see the phones fomatted as 650-123-4567
while user B
(650) 123-4567

Next, is area code a concept that applies universally to all the countries? Or it's just some prefix, that may have or might not have any meaning at all? Now that VOIP providers are increasingly becoming much more flexible with numbering system, the area code have no much sence to them any more. Since data in the database are long lived, doesn't it make more sence to store the bare information -- a string of numbers -- rather than the information decorated with some short lived and arbitrary methods? Received on Fri Oct 22 2004 - 18:31:54 CEST