Re: Disadvantages to using "text"

Hi Greg,
What are you trying to do with a postgres blob in ArcGIS?
-Postgres will be supported for ArcSDE in the 9.3 release of ArcGIS
- you can also try using the Interoperability extension to read/draw
data out of Postgres, or PostGIS on postgres without ArcSDE

Sincerely,
Kasia

Kasia Tuszynska
ArcSDE Product Engineer
ESRI

-----Original Message-----
From: pgsql-novice-owner(at)postgresql(dot)org
[mailto:pgsql-novice-owner(at)postgresql(dot)org] On Behalf Of Greg Cocks
Sent: Tuesday, May 13, 2008 9:58 AM
To: PostgreSQL List - Novice
Subject: Re: [NOVICE] Disadvantages to using "text"

... 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

--
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