Docs should clearly say that geometric types must be inserted as strings. - Mailing list pgsql-bugs

From pgsql-bugs@postgresql.org
Subject Docs should clearly say that geometric types must be inserted as strings.
Date
Msg-id 200011250819.eAP8J8S51723@hub.org
Whole thread Raw
Responses Re: Docs should clearly say that geometric types must be inserted as strings.
List pgsql-bugs
Michael G Schwern (schwern@pobox.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
stringand it worked. 

Sample Code


No file was uploaded with this report

pgsql-bugs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [INTERFACES] Re: no meaningful way to determine fe or beversion?
Next
From: pgsql-bugs@postgresql.org
Date:
Subject: Minor typos in the Geometric Functions docs (chapter 5)