On Tue, Jan 3, 2017 at 5:57 PM, Rahila Syed <rahilasye...@gmail.com> wrote: > Thank you all for inputs. > Kindly help me clarify the scope of the patch. > >>However, I thought the idea was to silently coerce affected columns from >>unknown to text. This doesn't look like the behavior we want: > > This patch prevents creation of relation with unknown columns and > in addition fixes the particular case of CREATE VIEW with literal columns > by coercing unknown to text only in this particular case. > > Are you suggesting extending the patch to include coercing from unknown to > text for all possible cases where a column of unknown type is being created? >
I guess, that's what Tom is suggesting. We need to do something to avoid throwing an error in the cases which do not throw error in earlier releases. We may just leave that warning as warning for now, and just tackle the view case in this patch. I would like everything being done in one patch, rather than this piece-meal approach. But delaying fix for views because it takes longer to work on other pieces may not be good either. -- Best Wishes, Ashutosh Bapat EnterpriseDB Corporation The Postgres Database Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
