Greetings,
I ran accross this problem upon upgrading our database from 7.0.3
to 7.1.2:
ERROR: UNIQUE constraint matching given keys for referenced
table "some_table" not found
Looking through the mailing lists i came across a couple of
discussions regarding this very same error:
ht
Bryan Field-Elliot <[EMAIL PROTECTED]> writes:
> I'm developing a GIS system on PostgreSQL. I need to store a table of
> points (latitude and longitude), and do queries such as "return all
> points enclosed with the given circle ((X,Y),R)".
You might care to look at
http://postgis.refractions
(Resending this as it was bounced for some
reason).
PostgreSQL's "timestamp with time zone"
implementation seems to fall short of the standard in the following
way.
The standard calls for this datatype to be stored
as a timestamp and a separate time zone displacement. This allows for
On Thu, 2 Aug 2001 [EMAIL PROTECTED] wrote:
> Well thankyou very much :-)
>
> The way you have done the dynamic query was my first try, but as long
> as it didn't work, I started messing it all.
>
> I have put it this way, but still returns the same ERROR message.
>
> I suppose that it
> I ran accross this problem upon upgrading our database from 7.0.3
> to 7.1.2:
>
>ERROR: UNIQUE constraint matching given keys for referenced
>table "some_table" not found
Yeah, we fixed this to follow spec (sql actually requires that the
references be to a unique or primary key const
On Wed Aug 01 00:12:53 CEST 2001
Dr. Evil ([EMAIL PROTECTED]) wrote :
Tankgirl, are you really really sure that you want to dynamicly add
columns to a table? You probably need to think through your data
definition if you are trying to do this, I think.
Well yes, I want to dynam
