| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Hall, Samuel L (Sam)" <sam(dot)hall(at)alcatel-lucent(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Problem with at_askml function in Postgis |
| Date: | 2013-06-26 16:29:23 |
| Message-ID: | 8776.1372264163@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Hall, Samuel L (Sam)" <sam(dot)hall(at)alcatel-lucent(dot)com> writes:
> I get this error
> ERROR: function st_askml(geometry) is not unique
> LINE 1: select st_askml(path) from paths where jobnumber = '20121491...
> ^
> HINT: Could not choose a best candidate function. You might need to add explicit type casts.
> Both st_askml(geometry) and st_askml(geometry, integer) are unique.
Perhaps st_askml(geometry, integer) has a default value for the integer
argument? If so, the variant without that argument should have been
removed. I'm suspicious that you've got some sort of upgrading glitch
that left both variants present when only one was needed.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dmitriy Igrishin | 2013-06-26 16:35:49 | Re: [HACKERS] Frontend/backend protocol improvements proposal (request). |
| Previous Message | Hall, Samuel L (Sam) | 2013-06-26 16:14:24 | Problem with at_askml function in Postgis |