ave an integer primary key on the table. This is easy to do:
>
> alter table add column gid serial (or bigserial);
>
> then make gid the primary key.
>
> --- On *Sat, 4/23/11, Sairam Krishnamurthy
> http://mc/compose?to=kmsram...@gmail.com>
> >* wrote:
>
>
> From: S
.
Cheers,
Brent Wood
--- On Sat, 4/23/11, Sairam Krishnamurthy wrote:
From: Sairam Krishnamurthy
Subject: Re: [postgis-users] Unique Constraint on Spatial Point violated
To: pcr...@pcreso.com
Cc: "PostGIS Users Discussion" ,
kulkarni.adity...@gmail.com
Date: Saturday, April 23, 2011, 7:4
;
> then make gid the primary key.
>
> --- On *Sat, 4/23/11, Sairam Krishnamurthy * wrote:
>
>
> From: Sairam Krishnamurthy
> Subject: [postgis-users] Unique Constraint on Spatial Point violated
> To: postgis-users@postgis.refractions.net
> Cc: "Aditya Kulkarni"
>
al keys, but
have an integer primary key on the table. This is easy to do:
alter table add column gid serial (or bigserial);
then make gid the primary key.
--- On Sat, 4/23/11, Sairam Krishnamurthy wrote:
From: Sairam Krishnamurthy
Subject: [postgis-users] Unique Constraint on Spatial Poi
All,
I am loading a table from a file. The file is really big and has
millions of rows. Table structure is described below:
lat : double precision (primary key)
lon: double precision (primary key)
spatialPoint: geometry (unique)
The file has lines of lat and lon: (lat,lon)
Since I am loading fr
