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

Re: Disadvantages to using "text" [ArcGIS]

From: "Greg Cocks" <gcocks(at)stoller(dot)com>
To: "Kasia Tuszynska" <ktuszynska(at)esri(dot)com>
Cc: "PostgreSQL List - Novice" <pgsql-novice(at)postgresql(dot)org>
Subject: Re: Disadvantages to using "text" [ArcGIS]
Date: 2008-05-13 17:26:43
Message-ID: 66F6CF82BF58CE4DB4285BE816B297E857F8D9@tribble.SMStoller.com (view raw or flat)
Thread:
Lists: pgsql-novice
Thanks for your reply...

I was working/experimenting with changing some of my VAR CHAR fields in
a PostgreSQL database to TEXT per this thread...

Via a direct database connection / ODBC link (or via an MS Access front
end and another ODBC), if these added "XY Location..." include a
TEXT-format field/s in the SELECT 'used' by ArcGIS (for symbology
differentiation, etc) then you get the "... no OID..." error and/or see
the fields listed as Binary Blob when you look at the attribute table in
ArcMap - so I had to change these specific fields back to a VAR CHAR
format...

Now that I know the workaround/constraint, no problem!   :-)

(Interestingly, at least to me, the WMS server I set up out of
PostgreSQL using MapServer is happy with the TEXT format when accessed
through ArcGIS/ArcCatalog... and of course OpenLayers doesn't mind at
all...)

I heard about the PostgreSQL support in 9.3 - but have also heard that
it is 'read only' connection? Will it support PostGIS? Other
functionality such as seen in ZigGIS?

We don't have the $$$$ for the Interoperability Extension very
unfortunately - we have some CAD datasets for some of our engineering
projects I'd love to connect to dynamically if we did!  :-)

Regards,
GREG COCKS
gcocks(at)stoller(dot)com
 



-----Original Message-----
From: Kasia Tuszynska [mailto:ktuszynska(at)esri(dot)com] 
Sent: Tuesday, May 13, 2008 11:04 AM
To: Greg Cocks; PostgreSQL List - Novice
Subject: RE: [NOVICE] 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

In response to

pgsql-novice by date

Next:From: A BDate: 2008-05-15 13:32:57
Subject: Transaction inside of functions
Previous:From: Bruce HyattDate: 2008-05-13 17:20:47
Subject: Re: Relation missing?

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