| From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | "Ferrell, Denise CTR NSWCDD, Z11 *EXTERN*" <denise(dot)ferrell(dot)ctr(at)navy(dot)mil>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: PK/FK impacts using text data type |
| Date: | 2015-01-10 19:14:09 |
| Message-ID: | A737B7A37273E048B164557ADEF4A58B34E5C673@ntex2010a.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Denise Ferrell wrote:
> We have been discussing whether or not to change all of our varchar (character varying)
> data types to text for ease of use in procedures/functions/triggers...
>
> Are there any impacts on keys by using text data type vs. character varying or character varying(n)?
The only useful thing about varchar is that it imposes a length constraint on a database field.
Values used for indexing have a length limit, so if you change an indexed column to text
somebody could try to insert values that will cause errors because the limit has been exceeded.
Also you application code cannot rely on a certain size limit any more.
If you are ok with that, go ahead and use text.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-01-10 19:20:50 | Re: PK/FK impacts using text data type |
| Previous Message | John Scalia | 2015-01-10 16:22:41 | Re: pg_upgrade from V9.3.3 to V9.4.0 |