From: | Martijn van Oosterhout <kleptog(at)cupid(dot)suninternet(dot)com> |
---|---|
To: | Gregory Wood <gregw(at)com-stock(dot)com> |
Cc: | PostgreSQL-General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Re: couple of general questions |
Date: | 2001-01-20 12:00:30 |
Message-ID: | 3A697DDE.6A85B236@cupid.suninternet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Gregory Wood wrote:
>
> > Does anyone else get annoyed when going on to an american site to
> > register or buy something and find that the state field is only
> > 2 characters long?
>
> Sorry, I didn't realize that many other countries had states... the only
> other frame of reference that I have is Canadian Provinces, which also have
> 2 character codes. Since we only do business with countries in the United
> States and Canada I'm woefully ignorant of international standards. I'd also
> like to apologise for our backwards use of the Imperial measurement
> system... but that one is not my fault.
Umm, sorry.
I must have come over somewhat stronger than I intended.
It was supposed to be just a passing comment. The reason
I picked up on it is because it's the first thing people
think of when looking for a reason for fixed length fields
and (as pointed out on this thread) it's not even valid
for the whole of the US.
Personally, for all DB systems I build now I just make
*every* text field type text and never use char()/varchar().
Everything time I think I've made it long enough, someone
comes up with an example that's longer. The performance
difference is marginal or non-existant.
Don't think I'm attacking you, I'm just trying to help...
--
Martijn van Oosterhout <kleptog(at)cupid(dot)suninternet(dot)com>
http://cupid.suninternet.com/~kleptog/
From | Date | Subject | |
---|---|---|---|
Next Message | Kovacs Zoltan Sandor | 2001-01-20 12:19:24 | Re: pl/pgSQL & transaction |
Previous Message | Lincoln Yeoh | 2001-01-20 11:54:43 | Re: RE: Why is there so much MySQL bashing??? |