Georg,
That sounds great. There was a memory leak fix in that function for some
users of unbuffered queries that you might want to leave in. I propose
the following function which is also a placeholder/reminder for the
future:
/* {{{ _restore_connection_defaults
*/
static int
I am commenting some entries from the ToDo here:
global
--
For PHP 4.3.0:
* Add aliases to functions to conform to new naming conventions, e.g.
str_to_upper().
some work done - many work needed here.
What about a new compiler define that allows enabling/disabling old function
Personally, I'd like to see the MySQL extension work again.
The issue: persistent connections are broken when used heavily.
Simple fix: _restore_connection_defaults() can be eliminated until fixed
properly.
So if the simple fix is implemented then all users of MySQL not using
transactions will
.
Regards,
Andrey
- Original Message -
From: Steven Roussey [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, November 14, 2002 8:58 PM
Subject: Re: [PHP-DEV] PHP 4.3 ToDo
Personally, I'd like to see the MySQL extension work again.
The issue: persistent connections are broken when used
On Thu, 14 Nov 2002, Steven Roussey wrote:
Personally, I'd like to see the MySQL extension work again.
The issue: persistent connections are broken when used heavily.
Simple fix: _restore_connection_defaults() can be eliminated until fixed
properly.
So if the simple fix is implemented
On Thursday 14 November 2002 19:58, Steven Roussey wrote:
Personally, I'd like to see the MySQL extension work again.
The issue: persistent connections are broken when used heavily.
Simple fix: _restore_connection_defaults() can be eliminated until fixed
properly.
As discussed with Derick
| * Change PHP error messages, so that they point to pages
|or sections
| in the PHP Manual.
|
Any particular concern as to how/when to point to the manual? I'm
assuming a HREF to http://www.php.net/funcname works, for every
function?
We simply have to convert php_error() calls to
