Re: [Fwd: Bug #16710 Updated: pg_exec to pg_query alias not mentioned in the NEWS file]Hi

At 10:54 4/29/2002 +0200, derick@php.net wrote:

On Mon, 29 Apr 2002, Yasuo Ohgaki wrote: Looks like I have edit News for 4.2.0... what do you think? +1

+1 What I don't get is that pg_result has been renamed to pg_fetch_result, while there is mysql_result. Does that mean we get mysql_fetch_result and mysql_result will be deprecated? The current online manual, doesn't reflect this. Attached a patch, on the current cvs, which is I think more user-friendly. Created by cvs diff *.xml >/tmp/pg.patch in phpdoc/en/reference/pgsql/functions

Derick -------- Original Message -------- Subject: Bug #16710 Updated: pg_exec to pg_query alias not mentioned in the NEWS file Date: 29 Apr 2002 00:34:02 -0000 From: jimw@php.net To: php-bugs@lists.php.net Newsgroups: php.bugs Followup-To: php.dev References: <bug-16710@bugs.php.net>

  ID:               16710
  Updated by:       jimw@php.net
  Reported By:      hs@cybertec.at
-Status:           Open
+Status:           Assigned
  Bug Type:         Feature/Change Request

Operating System: every system

  PHP Version:      4.2.0

-Assigned To:

+Assigned To:      yasuo

New Comment: assigning. Previous Comments: ------------------------------------------------------------------------ [2002-04-20 06:38:27] mfischer@php.net FYI: The manual page about pg_query() now mentiones that pg_exec() is still available. ------------------------------------------------------------------------ [2002-04-20 06:23:03] mfischer@php.net Reopened. Yasou, please enter a proper NEWS entry as there's no reference about this in the NEWS file (and light this up that the old function is still available, you see people get confused about this) . . . ------------------------------------------------------------------------ [2002-04-20 05:31:47] sander@php.net We decided to use pg_query() because it's more consistent with other database extensions (like mysql, which uses mysql_query()) The old function names still work and won't be removed soon. ------------------------------------------------------------------------ [2002-04-20 05:27:44] tal@php.net Reclassified. -Tal ------------------------------------------------------------------------ [2002-04-20 05:17:34] hs@cybertec.at I have just finished writing a book about PHP and PostgreSQL. After we have finished layouting the stuff we have seen that pg_exec has changed to pg_query for ABSOLUTELY NO USEFUL reason. In addition to that my company has written > 1000k of PHP/PostgreSQL code in the past and we have to port ALL applications to the new name. This will be chaotic and I cannot see a reason for the change. Was there no way of leaving the old name????? We will never ever use PHP in the future again because what we have to face is a microsoft like change destroying all books and all applications on the market. This IS a bug for all serious companies and developers and I hope that those who are responsible for the mess will read this message. Best regards,

            Hans-Jürgen Schönig
            (a former PHP programmer and author)

------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=16710&edit=1 -- PHP Quality Assurance Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php -----------------------------------------------------------------------

                 Did I help you? Consider a gift:
      http://www.amazon.co.uk/exec/obidos/registry/SLCB276UZU8B

-----------------------------------------------------------------------

              PHP: Scripting the Web - derick@php.net
                All your branches are belong to me!
            SRM: Script Running Machine - www.vl-srm.net

----------------------------------------------------------------------- -- PHP Quality Assurance Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php

Met vriendelijke groeten / With kind regards, Webmaster IDG.nl Melvyn Sopacua

Attachment: [application/octet-stream] pg.patch