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 |
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 <
dep...@depesz.com> wrote:
> On Wed, Sep 09,
*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
On Wed, Sep 9, 2015 at 7:51 PM, 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 } {
*>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