| From: | Ryan Murphy <ryanfmurphy(at)gmail(dot)com> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL DEV mailing list <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Adding type info etc for inheritance errmsg: "child table is missing column ..." |
| Date: | 2017-01-08 05:49:03 |
| Message-ID: | CAHeEsBd-4kX3G9xiE=_trjbm8M2o69KTxN9pxERLvOHSeFhO5w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> AFAICS, what Ryan is after would be better served by a separate tool that
> would produce a "diff" of the two tables' schemas.
Related to the other idea of seeing the problems that exist in all the
> columns (instead of one column at a time), I think it'd be reasonable to
> have a SRF that spit out everything you'd need to fix to allow inheritance
> to be added. A schema diff won't know what specifically has to match, but
> our code does.
>
>
Sure, I think that's totally true that I could just make a
Set-Returning-Function (that's what SRF stands for right?) that would
accomplish this. I'll try that path instead for now.
Thanks guys!
Ryan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2017-01-08 06:03:51 | Re: merging some features from plpgsql2 project |
| Previous Message | Pavel Stehule | 2017-01-08 05:45:46 | Re: merging some features from plpgsql2 project |