Re: [PATCHES] document plperl argument and return value representation

Andrew Dunstan wrote: > > > Alvaro Herrera wrote: > >Andrew Dunstan wrote: > > > >>The attached docs patch makes clearer how arguments and return values in > >>pl/perl are escaped. This is to clarify the situation that Theo > >>Schlossnagle recently reported on -bugs. > >> > > > >I find t

Re: [PATCHES] document plperl argument and return value representation

Andrew Dunstan <[EMAIL PROTECTED]> writes: > Is this better? I suggest bytea -> bytea, otherwise seems fine. regards, tom lane ---(end of broadcast)--- TIP 6: explain analyze is your friend

Re: [PATCHES] document plperl argument and return value representation

Alvaro Herrera wrote: Andrew Dunstan wrote: The attached docs patch makes clearer how arguments and return values in pl/perl are escaped. This is to clarify the situation that Theo Schlossnagle recently reported on -bugs. I find the mix of arguments and results a bit confusing. May

Re: [PATCHES] document plperl argument and return value representation

Andrew Dunstan wrote: > > The attached docs patch makes clearer how arguments and return values in > pl/perl are escaped. This is to clarify the situation that Theo > Schlossnagle recently reported on -bugs. I find the mix of arguments and results a bit confusing. Maybe you could put them in s

[PATCHES] document plperl argument and return value representation

The attached docs patch makes clearer how arguments and return values in pl/perl are escaped. This is to clarify the situation that Theo Schlossnagle recently reported on -bugs. If there's no objection I will apply this. cheers andrew ? plperldoc.patch Index: plperl.sgml ===