[postgis-users] alpha GT2 Web Map Server with PostGIS support

[Paul Ramsey]

A counter point to this one is that oids are *not* indexed by default. 
The "best" first choice for a uid would be the column which is flagged 
as the "primary key" as that column is both guaranteed to be unique and 
indexed. Failing that, the oid would be a reasonable backup, since it is 
at least guaranteed to be unique.

P.

chodgson at refractions.net wrote:
> You might be better to use the OID value for the feature identifier. After all, 
> it is entirely possible to have a table with only a geometry column. The OID 
> value is what the mapserver connector uses by default (but you can specify 
> another column if you want). The OID is an "invisible" column that postgres 
> adds to all tables, if you didn't know - it's the "object identifier" and is at 
> least unique for all of the rows in a given table.
> 
> I would highly recommend making this a configurable option, as your identifying 
> column should probably have an index, as it is silly to have to index another 
> column when you already have a perfectly good, indexed, unique value.
> 
> Chris Hodgson



-- 
       __
      /
      | Paul Ramsey
      | Refractions Research
      | Email: pramsey at refractions.net
      | Phone: (250) 885-0632
      \_