[postgis-devel] PostGIS 1.4 SVN geometry parser hints

[Paul Ramsey]

But frankly, I like your approach just fine. The floating carat "^" is
the other traditional approach, but I find they never really line up
well with the context, and so become useless. Between your truncated
context and position number, things should be fine.

P.

On Wed, Oct 15, 2008 at 12:24 PM, Paul Ramsey <pramsey at cleverelephant.ca> wrote:
> Parse errors near the front lose context... and the position number is
> off a bit.
>
> postgis2=# select 'MULTIPOYGON(((0 0, 0 0, 0 0,0 0),(0 0, 0 0, 0 0,0
> 0),(0 0, 0 0, 0 0,0 0),(0 0, 0 0, 0 0,0 0),(0 0, 0 0, 0 0,0
> 0)))'::geometry;
> ERROR:  parse error - invalid geometry
> HINT:  "" <-- parse error at position 0 within geometry
>
>
> On Wed, Oct 15, 2008 at 12:22 PM, Paul Ramsey <pramsey at cleverelephant.ca> wrote:
>> Why does this error start with "...?gs"?
>>
>> postgis2=# select 'MULTIPOLYGON(((0 0, 0 0, 0 0,0 0),(0 0, 0 0, 0 0,0
>> 0),(0 0, 0 0, 0 0,0 0),(0 0, 0 0, 0 0,0 0),(0 0, 0 , 0 0,0
>> 0)))'::geometry;
>> ERROR:  parse error - invalid geometry
>> HINT:  "...?gs, 0 0,0 0),(0 0, 0 0, 0 0,0 0),(0 0, 0 ," <-- parse
>> error at position 103 within geometry
>>
>> P.
>>
>