SEO
vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
04-18-2008, 10:00 AM
| ||||
| ||||
 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 ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings      |
|
04-18-2008, 10:00 AM
| |||
| |||
| Re: 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 separate paragraphs. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match |
|
04-18-2008, 10:00 AM
| |||
| |||
| Re: 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. Maybe you > could put them in separate paragraphs. > > Is this better? I also took the opportunity to replace an unbalanced quote mark that was screwing up the syntax highlighting. cheers andrew ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org |
|
04-18-2008, 10:00 AM
| |||
| |||
| Re: document plperl argument and return value representation Andrew Dunstan <andrew@dunslane.net> writes: > Is this better? I suggest bytea -> <type>bytea</>, otherwise seems fine. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend |
|
04-18-2008, 10:00 AM
| ||||
| ||||
| Re: 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 the mix of arguments and results a bit confusing. Maybe you > >could put them in separate paragraphs. > > Is this better? Yup, looks very nice. This message also serves to test whether I removed the annoying Mail-Followup-To header. It was actually a _feature_ of mutt (followup_to, which fired when I replied to a list to which I'm subscribed), which I disabled. Sorry about that. ETOOMANYWHICH, sorry about that as well :-) -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster |
Linear Mode
