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.
Docs should clearly say that geometric types must be inserted as strings.
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.
No file was uploaded with this report
pgsql-bugs by date
|Next:||From: pgsql-bugs||Date: 2000-11-25 08:22:13|
|Subject: Minor typos in the Geometric Functions docs (chapter 5)|
|Previous:||From: Bruce Momjian||Date: 2000-11-25 04:32:23|
|Subject: Re: [INTERFACES] Re: no meaningful way to determine fe or beversion?|