> On Mon, Jan 13, 2003 at 11:59:33AM +0800, Christopher Kings-Lynne wrote:
> >
> > I will, but unfortunately the damage has already been done...since I
have to
> > support 7.3 anyway, fixing the above problem will actually make my life
> > harder, not easier...
Another issue to consider is that
On Mon, Jan 13, 2003 at 11:59:33AM +0800, Christopher Kings-Lynne wrote:
>Tom Lane writes:
> >
> > Feel free to contribute some code.
>
> I will, but unfortunately the damage has already been done...since I have to
> support 7.3 anyway, fixing the above problem will actually make my life
> harder,
> "Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> > Is there some reason why pg_get_constraintdef only supports Foreign Key
> > constraints?
>
> Lack of implementation effort --- the original definition/implementation
> was FK-specific, but now, as the code says,
>
> * XXX The present impl
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> Is there some reason why pg_get_constraintdef only supports Foreign Key
> constraints?
Lack of implementation effort --- the original definition/implementation
was FK-specific, but now, as the code says,
* XXX The present implementation onl
Is there some reason why pg_get_constraintdef only supports Foreign Key
constraints? Why not have it output ALTER TABLE commands for UNIQUE and
PRIMARY KEY constraints? That would make my life so much easier for
phpPgAdmin and also pg_dump could be simplified quite considerably...?
Chris
-
