Re: RFC: PostgreSQL Function Rename (again ;)

On Sat, 15 Dec 2001, Yasuo Ohgaki wrote: > Hi all, > > I've messed up my request for comments last time. > I think some of you are expecting me to post again ;) > Some names are changed also. > > I would like to here your comments about new function > names. I'll commit the change at once, since > async functions are commited already, other changes are > local to it's functions. > > Please reply if you have comments. > > New functions (including async functions) > pg_send_query > pg_cancel_qeury > pg_get_result > pg_connection_busy > pg_connection_status > pg_connection_reset > pg_result_error > pg_copy_to (Patch by Youichi Iwakiri) > pg_copy_from (Patch by Youichi Iwakiri) > pg_escape_string (PostrreSQL 7.2 only) > pg_escape_bytea (PostgreSQL 7.2 only) > pg_loseek > pg_lotell > Why not pg_lo_seek and pg_lo_tell ? > API change > pg_loimport, pg_loexport now takes connection as 1st parameter. > Old API still works with NOTICE error message. > Again, shouldn't the names comply with the (new?) coding standards ? pg_lo_import and pg_lo_export should be the names IMHO. I saw some other functions like pg_loclose and etc. Shouldn't they be changed also ? Joao -- João Prado Maia <jpm@phpbrasil.com> http://phpbrasil.com - php com um jeitinho brasileiro -- Precisando de consultoria em desenvolvimento para a Internet ? Impleo.net - http://impleo.net/?lang=br