The tickets view restricts which tickets can be seen by the schema.
9.3 must have created the view in the same column order as the table (which is the case looking at one of our 9.3 databases which we have not updated yet), which is why we never saw the issue before.
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;