Stephen,
OK. I guess this is a good solution. I just thought OIDs as I
had some recent problems getting Postgis data displayed in
QGIS and PGAdmin (clients). If you don't have a primary key,
it tries to use OIDs for unique identifier. So you can tackle
2 problems in one go.
GL
Stephen Frost wrote:
* Guido Lemoine ([EMAIL PROTECTED]) wrote:
Use postgresql OIDs. These are "unique" object IDs.
Do *not* use postgresql OIDs.
Create a sequence and add a column to each table which defaults to
nextval() on that sequence. He's only talking about 3 tables anyway.
Thanks,
Stephen
------------------------------------------------------------------------
_______________________________________________
postgis-users mailing list
[email protected]
http://postgis.refractions.net/mailman/listinfo/postgis-users
--
----------------------------------------------------------------
Guido Lemoine
Joint Research Centre, European Commission
Institute for the Protection and Security of the Citizen (IPSC)
Unit: Support to External Security
Via E. Fermi, 1 TP 267 Ispra 21020 (VA), Italy
Tel. +39 0332 786239 (direct line) Fax. +39 0332 785154
WWW: http://ses.jrc.it
----------------------------------------------------------------
Disclaimer:
Views expressed are those of the individual and do not represent
the views of the European Commission
_______________________________________________
postgis-users mailing list
[email protected]
http://postgis.refractions.net/mailman/listinfo/postgis-users
