Thread

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

   PostgreSQL Bugs List <pgsql-bugs@postgresql.org> — 2000-11-25T08:19:08Z

   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 string and it worked.
   
   Sample Code
   
   
   No file was uploaded with this report
   
   
   

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

   Peter Eisentraut <peter_e@gmx.net> — 2000-11-25T15:52:05Z

   > Docs should clearly say that geometric types must be inserted as strings.
   
   http://www.postgresql.org/users-lounge/docs/7.0/user/syntax539.htm#AEN579
   
   -- 
   Peter Eisentraut      peter_e@gmx.net       http://yi.org/peter-e/