Re: Bugs with like_option in CREATE TABLE

My apologies.

I made a test case but this time it worked. I must have had a brain fart
while I was working on this yesterday. Well, at least I am getting used to
the taste of eating crow. :)

On Thu, Sep 10, 2015 at 5:56 AM, hubert depesz lubaczewski <
depesz(at)depesz(dot)com> wrote:

> On Wed, Sep 09, 2015 at 07:51:48PM -0400, Melvin Davidson wrote:
> > *O/S = Windows 10PostgreSQL 9.2.10, compiled by Visual C++ build 1600,
> > 32-bit*
> > http://www.postgresql.org/docs/9.1/interactive/sql-createtable.html
> >
> > and like_option is:
> > { INCLUDING | EXCLUDING } { DEFAULTS | CONSTRAINTS | INDEXES | STORAGE |
> > COMMENTS | ALL }
> > 1. INCLUDING CONSTRAINTS does not bring over the Foreign Keys
>
> Of course it doesn't. It's documented in the page you linked:
>
> "Not-null constraints are always copied to the new table. CHECK
> constraints will only be copied if INCLUDING CONSTRAINTS is specified;
> other types of constraints will never be copied"
>
> > 2. INCLUDING ALL does not work and generates an ERROR;*
>
> Works for me. Please provide a test case that can be used to see the
> error.
>
> Best regards,
>
> depesz
>
> --
> The best thing about modern society is how easy it is to avoid contact
> with it.
>
> http://depesz.com/
>

--
*Melvin Davidson*
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.