From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | ib(at)ianbellsoftware(dot)com |
Cc: | "'Adrian Klaver'" <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: PGAdmin4 debugger - unable to call ltree functions |
Date: | 2018-04-26 22:18:14 |
Message-ID: | 6461.1524781094@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Ian Bell" <ib(at)ianbellsoftware(dot)com> writes:
> I just tried your suggestion and it generates the same error. For
> verification, here is the function run in the debugger.
I just realized that "syntax error at position N" is *not* the exact
spelling you would get from a syntax error in PG's main parser, which
I think is what we were all assuming this'd trace down to somehow.
What it is is the (very poorly chosen) message you get if either
ltree_in() or lquery_in() doesn't like what it's been handed.
So basically, the problem here is that TestLtree() is being called
with a string that isn't a valid ltree representation. You haven't
shown us what you are doing on that end, but for example I can
duplicate the error message with
# select text2ltree(' ');
ERROR: syntax error at position 0
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Ian Bell | 2018-04-26 22:47:31 | RE: PGAdmin4 debugger - unable to call ltree functions |
Previous Message | Adrian Klaver | 2018-04-26 22:04:27 | Re: PGAdmin4 debugger - unable to call ltree functions |