Re: Bugs with like_option in CREATE TABLE

From: Melvin Davidson <melvin6925(at)gmail(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Bugs with like_option in CREATE TABLE
Date: 2015-09-10 01:21:00
Message-ID: CANu8Fiyi-3wshf3hkvkoDngp_3AcY7rOPR+cxKbBjr5DzSngSg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

*>1. INCLUDING CONSTRAINTS does not bring over the Foreign Keys*

>Not a bug since the documentation states that the only additional
constraints that are brought over are check constraints.​ Not Null
constraints are always brought
>over.

Hmmm, The document would be a lot clearly if it simply stated Foreign Keys
are NOT brought over.
Anyhow, I've found a work around for that,

*>2. INCLUDING ALL does not work and generates an ERROR;*

​>For kicks does writing it out in long form work?

No. I tried INCLUDING ALL and just ALL by itself, both create a syntax
error.

On Wed, Sep 9, 2015 at 8:51 PM, David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:

> On Wed, Sep 9, 2015 at 7:51 PM, Melvin Davidson <melvin6925(at)gmail(dot)com>
> 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*
>>
>
> ​Not a bug since the documentation states that the only additional
> constraints that are brought over are check constraints.​ Not Null
> constraints are always brought over.
>
> ​"""
> 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. Also, no distinction is made between
> column constraints and table constraints — when constraints are requested,
> all check constraints are copied.
> """​
>
>
>> *2. INCLUDING ALL does not work and generates an ERROR;*
>>
>
> ​For kicks does writing it out in long form work?
>
> """
> INCLUDING ALL is an abbreviated form of INCLUDING DEFAULTS INCLUDING
> CONSTRAINTS INCLUDING INDEXES INCLUDING STORAGE INCLUDING COMMENTS.
> """
>
> David J.
>
>

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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jeff Janes 2015-09-10 04:40:43 Re: GIN Trigram Index Size
Previous Message David G. Johnston 2015-09-10 00:51:05 Re: Bugs with like_option in CREATE TABLE