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-13 16:58:26 |
Message-ID: | 66F6CF82BF58CE4DB4285BE816B297E857F8CA@tribble.SMStoller.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
... and I am finding some of the software I am using, namely ArcGIS,
doesn't "like" the PostgreSQL 'text' format as it sees it as a Binary
Blob.... so direct links via ODBC, etc can "die.."
What a pity...
Regards,
GREG COCKS
gcocks(at)stoller(dot)com
-----Original Message-----
From: Greg Cocks [mailto:gcocks(at)stoller(dot)com]
Sent: Wednesday, May 07, 2008 11:48 AM
To: PostgreSQL List - Novice
Subject: Re: [NOVICE] Disadvantages to using "text"
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.
--
Sent via pgsql-novice mailing list (pgsql-novice(at)postgresql(dot)org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-novice
From | Date | Subject | |
---|---|---|---|
Next Message | Kasia Tuszynska | 2008-05-13 17:04:08 | Re: Disadvantages to using "text" |
Previous Message | A. Kretschmer | 2008-05-13 13:53:27 | Re: Relation missing? |