Skip site navigation (1) Skip section navigation (2)

Re: Disadvantages to using "text"

From: "Greg Cocks" <gcocks(at)stoller(dot)com>
To: "PostgreSQL List - Novice" <pgsql-novice(at)postgresql(dot)org>
Subject: Re: Disadvantages to using "text"
Date: 2008-05-07 17:48:02
Message-ID: 66F6CF82BF58CE4DB4285BE816B297E857F4D3@tribble.SMStoller.com (view raw or flat)
Thread:
Lists: pgsql-novice
One disadvantage is that if you are using MS Access as a front-end via
ODBC / linked tables, you can not do joins on fields set as text (in
queries, etc) 
 

-----Original Message-----
From: Frank Bax [mailto:fbax(at)sympatico(dot)ca] 
Sent: Wednesday, May 07, 2008 10:55 AM
To: PostgreSQL List - Novice
Subject: Re: [NOVICE] Disadvantages to using "text"

Aurynn Shaw wrote:
> Internally, Postgres treats a VARCHAR(n) as a TEXT with a CHECK 
> constraint applied to it, so VARCHAR is going to be slightly slower to
use.


Don't you mean VARCHAR(n) will be slightly slower on UPDATES.

In response to

Responses

pgsql-novice by date

Next:From: Alvaro HerreraDate: 2008-05-07 18:15:14
Subject: Re: [NOVICE] encoding problems
Previous:From: Bruce MomjianDate: 2008-05-07 17:46:11
Subject: Re: [NOVICE] encoding problems

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group