Postgres Pro
Downloads
Home   >   mailing lists

Re: Getting rid of SQLValueFunction - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Getting rid of SQLValueFunction
Date
Msg-id 3127103.1666321822@sss.pgh.pa.us
Whole thread Raw
In response to Re: Getting rid of SQLValueFunction  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Getting rid of SQLValueFunction  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
Tree view 
Michael Paquier <michael@paquier.xyz> writes:
> But the patch enforces the attribute name to be the underlying
> function name, switching the previous "current_catalog" to
> "current_database".

The entire point of SQLValueFunction IMO was to hide the underlying
implementation(s).  Replacing it with something that leaks
implementation details does not seem like a step forward.

            regards, tom lane

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Getting rid of SQLValueFunction
Next
From: Michael Paquier
Date:
Subject: Re: Getting rid of SQLValueFunction