Re: Database.Schema.Table

From: jmz <mxav1111(at)gmail(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Database.Schema.Table
Date: 2019-07-21 04:54:23
Message-ID: CABJ1pN8aWZ9h4LTXnWYpir=DdrcZYmOAS7a5HO1LRUZZW92ymw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Thank you for the clarification David. I really thought this would be
easier to implement since rest of the architecture (within DB) doesn't need
any (or little) change.

Max.

On Sat, Jul 20, 2019, 19:35 David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
wrote:

> On Saturday, July 20, 2019, jmz <mxav1111(at)gmail(dot)com> wrote:
>>
>> Does any one know if database.schema.table syntax would make it to
>> Release 12?
>>
>
> No. The lack of an entry in the beta release notes (or relevant
> documentation) and probably the same error when attempting it on version 12
> makes this clear.
>
> There is no pending patch or even, IIRC, recent discussion on making this
> potentially a thing. My understanding is the current architecture of the
> product makes implementing such a capability prohibitively expensive in
> terms of both time and risk.
>
> David J.
>
>

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Avin Kavish 2019-07-21 05:50:35 Re: Database.Schema.Table
Previous Message David G. Johnston 2019-07-21 02:48:13 Re: How do I alter an existing column and add a foreign key which is a Primary key to a table?