Re: How do i get the Ref cursor returned by an oracle procedure in php?
| From: | Hannes Magnusson | Date: | Wed, 05 Nov 2008 11:25:13 +0000 |
| Subject: | Re: How do i get the Ref cursor returned by an oracle procedure in php? | ||
| References: | 1 2 | Groups: | php.pecl.dev |
| Request: | Send a blank email to pecl-dev+get-5854@lists.php.net to get a copy of this message | ||
(trying again, SURBL is being an idiot again)
On Mon, Nov 3, 2008 at 19:41, Christopher Jones
<christopher.jones@oracle.com> wrote:
>
> This isn't a support forum. Please post to php-db@lists.php.net
>
> (Write a wrapper function in PL/SQL that pipes the output. I'll
> be blogging on this in a few days:
> http://blogs.oracle.com/opal/).
I like good PHP blogging, but stuff that deserve documentation should
be in the documentations.
Writing "articles", "FAQ", "tips&tricks chapters" and such things
for
the manual is very easy. The only difference (to "regular" blogging)
is maybe the wording and possibly the structure.
I would really appreciate if core and pecl developers would actually
help the rest of the community by doing it.. but there are at least 8
reasons why you shouldn't write for the php.net manual[1] which you
should be aware of before doing so.
Don't take it personally Chris, you were just an easy target right now :)
If anyone is interested I can write up an step-by-step-by-step
(American tutorial style)
guide/tutorial/article/whateveryouwanttocallit on how to write such
things, from A-Z. Including how to fetch the sources and building the
stuff (similar to
http://doc.php.net/php/dochowto/article.thequicky.exceptions.php).
-Hannes
[1] http://bjori. blogspot
.com/2007/10/8-reasons-why-you-should-not-write-for.html