From: | Culley Harrelson <culleyharrelson(at)yahoo(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: couple of general questions |
Date: | 2001-01-19 15:43:12 |
Message-ID: | 20010119154312.47656.qmail@web9605.mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
------------------------
Best, depending on the scenario. In cases where you
are using a fixed number
of characters, there's no need for the overhead of a
varchar. For instance
if you are storing state abbreviations, they will
ALWAYS be 2 characters.
The database can look up those fixed fields faster.
But if you are storing
full state names, it would be a waste to have all
those passing spaces so
that you could fit Mississippi with Maine. All that
being said, it's my
understanding that there will be no benefit to using
the CHAR type over the
VARCHAR type in 7.1 due to architectural changes.
-----------------------------------
Is there any difference between varchar and text other
than varchar places a
cap on the number of characters?
Culley
__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Nathan Heagy | 2001-01-19 15:46:50 | Selects with Array member |
Previous Message | Gordan Bobic | 2001-01-19 15:40:35 | Re: Another optimizer question |