From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | George Woodring <george(dot)woodring(at)iglass(dot)net>, pavel(dot)stehule(at)gmail(dot)com |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Plpgsql search_path issue going from 9.3 to 9.6 |
Date: | 2018-11-13 14:45:49 |
Message-ID: | f9c5644c-bf68-19a8-e563-21cdf642e95f@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 11/13/18 6:27 AM, George Woodring wrote:
> I think the issue is that the function is not putting the data into the
> tickets%ROWTYPE correctly. When I do \d on public.tickets and
> iss-hackers.tickets, the columns are in a different order.
>
>
> The error message is saying column2 is not a timestamp, which the public
> table is a timestamp for column2. If I change my SELECT in the function
> from SELECT * to SELECT opendate I can fix my issue easily.
Or change this:
SELECT * INTO ticket FROM tickets WHERE ticketsid=tid;
to:
SELECT * INTO ticket FROM public.tickets WHERE ticketsid=tid;
This will match the ROWTYPE:
ticket public.tickets%ROWTYPE;
>
> George
> iGLASS Networks
> www.iglass.net <http://www.iglass.net>
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | George Woodring | 2018-11-13 14:54:38 | Re: Plpgsql search_path issue going from 9.3 to 9.6 |
Previous Message | Adrian Klaver | 2018-11-13 14:43:20 | Re: Plpgsql search_path issue going from 9.3 to 9.6 |