| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | "Jonah H(dot) Harris" <jharris(at)tvi(dot)edu> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Inline PL/pgSQL |
| Date: | 2005-05-09 17:58:27 |
| Message-ID: | 427FA4C3.4080107@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>
> As for implementation, I think it would obviously be best to leave
> plpgsql on its own as a PL but maybe change BEGIN and DECLARE in the
> normal parser and have the system generate/execute a function on the
> fly. Or, maybe it would be better to integrate plpgsql. Or, I may just
> be crazy.
>
> Would anyone else ever benefit from inline functions?
Well I could see inline functions being useful for debugging a function
during development but I don't think I would want a bunch of plPGSQL
mucking up my pretty SQL :)
Sincerely,
Joshua D. Drake
--
Your PostgreSQL solutions company - Command Prompt, Inc. 1.800.492.2240
PostgreSQL Replication, Consulting, Custom Programming, 24x7 support
Managed Services, Shared and Dedication Hosting
Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2005-05-09 18:08:13 | Re: Inline PL/pgSQL |
| Previous Message | Jonah H. Harris | 2005-05-09 17:44:23 | Inline PL/pgSQL |