| From: | daveg <daveg(at)sonic(dot)net> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, "Patches (PostgreSQL)" <pgsql-patches(at)postgresql(dot)org>, Andrew Chernow <ac(at)esilo(dot)com> |
| Subject: | Re: libpq object hooks |
| Date: | 2008-05-14 19:47:27 |
| Message-ID: | 20080514194727.GT5673@sonic.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
On Wed, May 14, 2008 at 10:52:43AM -0400, Bruce Momjian wrote:
>
> One idea would be to add the libpq hooks but not document them. This
> way, we can modify or remove the API as needed in the future. As
> libpqtypes matures and we are sure what the API should be, we can
> document it as stable and permanent.
-1
Perhaps it is just me, but undocumented interface are evil. Simply document
it with the changable bits labled as such.
-dg
--
David Gould daveg(at)sonic(dot)net 510 536 1443 510 282 0869
If simplicity worked, the world would be overrun with insects.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-05-14 19:48:36 | Re: What to do with inline warnings? |
| Previous Message | Gregory Stark | 2008-05-14 19:35:37 | Re: What to do with inline warnings? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2008-05-14 20:30:35 | Re: libpq object hooks |
| Previous Message | Andrew Chernow | 2008-05-14 18:09:09 | Re: libpq object hooks |