Tom Lane e07e2a40bd Improve error messages in ltree_in and lquery_in. ... Ensure that the type name is mentioned in all cases (bare "syntax error" isn't that helpful). Avoid using the term "level", since that's not used in the documentation. Phrase error position reports as "at character N" not "in position N"; the latter seems ambiguous, and it's certainly not how we say it elsewhere. For the same reason, make the character position values be 1-based not 0-based. Provide a position in more cases. (I continued to leave that out of messages complaining about end-of-input, where it seemed pointless, as well as messages complaining about overall input complexity, where fingering any one part of the input would be arbitrary.) Discussion: https://postgr.es/m/15582.1585529626@sss.pgh.pa.us		2020-03-31 11:14:42 -04:00
..
expected
sql
.gitignore
ltree_plpython2u--1.0.sql
ltree_plpython2u.control
ltree_plpython3u--1.0.sql
ltree_plpython3u.control
ltree_plpython.c
ltree_plpythonu--1.0.sql
ltree_plpythonu.control
Makefile