Docs should clearly say that geometric types must be inserted as strings.

From: pgsql-bugs(at)postgresql(dot)org
To: pgsql-bugs(at)postgresql(dot)org
Subject: Docs should clearly say that geometric types must be inserted as strings.
Date: 2000-11-25 08:19:08
Message-ID: 200011250819.eAP8J8S51723@hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Michael G Schwern (schwern(at)pobox(dot)com) reports a bug with a severity of 4
The lower the number the more severe it is.

Short Description
Docs should clearly say that geometric types must be inserted as strings.

Long Description
Its not clear in the documentation whether geometric data types are to be dealt with as strings or as barewords in SQL. A nice, clear example of INSERTing a path or polygon would be nice in the docs.

This isn't a bug, but it made me think PostgreSQL was buggy as I initialy tried:

INSERT INTO Foo (ID, Chain) VALUES (42, [(1,1),(2,2)])

And got a syntax error about the '['. After banging my head against the wall for a couple days, I tried the path as a string and it worked.

Sample Code

No file was uploaded with this report

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message pgsql-bugs 2000-11-25 08:22:13 Minor typos in the Geometric Functions docs (chapter 5)
Previous Message Bruce Momjian 2000-11-25 04:32:23 Re: [INTERFACES] Re: no meaningful way to determine fe or beversion?