From: | Melvin Davidson <melvin6925(at)gmail(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | Alexander Farber <alexander(dot)farber(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: ERROR: type " " does not exist |
Date: | 2017-06-12 20:41:04 |
Message-ID: | CANu8FizvgyW+k6ukiW+mHnc0ss1wiDQdh0y43jJ5O=vcdM=Qpw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Jun 12, 2017 at 4:28 PM, David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> On Mon, Jun 12, 2017 at 1:03 PM, Alexander Farber <
> alexander(dot)farber(at)gmail(dot)com> wrote:
>
>> ERROR: type " " does not exist at character 149
>>
>
> Nothing shown would explain what you are seeing. Of course, white-space
> issues are really hard to communicate via email.
>
> As a brute-force suggestion I'd say you want to re-write the function one
> statement at a time to confirm that, one, you are indeed calling the
> correct function body, and, two figure out the exact statement that is
> problematic. I'd do this via copy-paste until the problem statement
> appears then I'd re-type in the problem statement by hand.
>
> There are probably more efficient ways to do all this but given a lack of
> experience and a relatively small function I'd spend more effort trying to
> figure out a better way than just doing it brute force.
>
> David J.
>
>
*You did not state the O/S you are using, but if it's LINUX, just use vi
and do a "set list".*
*That should reveal any strange characters that might be the cause,*
--
*Melvin Davidson*
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2017-06-12 20:53:32 | Re: ERROR: type " " does not exist |
Previous Message | David G. Johnston | 2017-06-12 20:28:49 | Re: ERROR: type " " does not exist |