Bug #16710 Updated: pg_exec to pg_query alias not mentioned in the NEWS file
ID: 16710 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Assigned +Status: Closed Bug Type: Feature/Change Request Operating System: every system PHP Version: 4.2.0 Assigned To: yohgaki New Comment: This bug has been fixed in CVS. You can grab a snapshot of the CVS version at http://snaps.php.net/ NEWS entry has been added. It listed as 4.2.0 change. Previous Comments: [2002-04-28 20:34:02] [EMAIL PROTECTED] assigning. [2002-04-20 06:38:27] [EMAIL PROTECTED] FYI: The manual page about pg_query() now mentiones that pg_exec() is still available. [2002-04-20 06:23:03] [EMAIL PROTECTED] 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] [EMAIL PROTECTED] 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] [EMAIL PROTECTED] Reclassified. -Tal The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/16710 -- Edit this bug report at http://bugs.php.net/?id=16710edit=1
Bug #16710 Updated: pg_exec to pg_query alias not mentioned in the NEWS file
ID: 16710 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -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] [EMAIL PROTECTED] FYI: The manual page about pg_query() now mentiones that pg_exec() is still available. [2002-04-20 06:23:03] [EMAIL PROTECTED] 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] [EMAIL PROTECTED] 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] [EMAIL PROTECTED] Reclassified. -Tal [2002-04-20 05:17:34] [EMAIL PROTECTED] 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=16710edit=1
Bug #16710 Updated: pg_exec to pg_query alias not mentioned in the NEWS file
ID: 16710 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Assigned Bug Type: Feature/Change Request Operating System: every system PHP Version: 4.2.0 -Assigned To: yasuo +Assigned To: yohgaki Previous Comments: [2002-04-28 20:34:02] [EMAIL PROTECTED] assigning. [2002-04-20 06:38:27] [EMAIL PROTECTED] FYI: The manual page about pg_query() now mentiones that pg_exec() is still available. [2002-04-20 06:23:03] [EMAIL PROTECTED] 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] [EMAIL PROTECTED] 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] [EMAIL PROTECTED] Reclassified. -Tal The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/16710 -- Edit this bug report at http://bugs.php.net/?id=16710edit=1
Bug #16710 Updated: pg_exec to pg_query alias not mentioned in the NEWS file
ID: 16710 Updated by: [EMAIL PROTECTED] -Summary: pg_exec to pg_query Reported By: [EMAIL PROTECTED] -Status: Bogus +Status: Open Bug Type: Feature/Change Request Operating System: every system PHP Version: 4.2.0 New Comment: 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) . . . Previous Comments: [2002-04-20 05:31:47] [EMAIL PROTECTED] 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] [EMAIL PROTECTED] Reclassified. -Tal [2002-04-20 05:17:34] [EMAIL PROTECTED] 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=16710edit=1
Bug #16710 Updated: pg_exec to pg_query alias not mentioned in the NEWS file
ID: 16710 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Open Bug Type: Feature/Change Request Operating System: every system PHP Version: 4.2.0 New Comment: FYI: The manual page about pg_query() now mentiones that pg_exec() is still available. Previous Comments: [2002-04-20 06:23:03] [EMAIL PROTECTED] 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] [EMAIL PROTECTED] 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] [EMAIL PROTECTED] Reclassified. -Tal [2002-04-20 05:17:34] [EMAIL PROTECTED] 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=16710edit=1
