Have you already tried to patch the Zend/zend_list.c file and recompile it?
there is a known problem with persistent connections,
read this:
http://groups.google.com/groups?hl=en&lr=&safe=off&ic=1&th=8810708445e328bb&;
seekd=939114469#939114469

and this: http://marc.theaimsgroup.com/?l=php-dev&m=97858730928909&w=2

it sure helped here, from the more than 40k errors with mysql we went
down to approx 1000 errors/daily.

Kees

-----Oorspronkelijk bericht-----
Van: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]Namens
Michael Kimsal
Verzonden: Friday, April 06, 2001 3:40 PM
Aan: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
Onderwerp: [PHP] mssql_pconnect issues?


Very strange.  I've noticed some integrity issues using mssql_pconnect,
but we don't explicitly use transactions in any case, so it may not
even go that deep.

I wonder if the odbc functions have this issue - anyone have any ideas?

[EMAIL PROTECTED] wrote:

> Hello Michael
>
> Some people have reported with the ADODB database class library that they
> were having problems with inserts and updates when using mssql_pconnect.
> Switching to regular mssql_connect the problems disappeared.
>
> I suspect it has something to do with persistent connections having
> inconsistent transaction handling settings. Eg.
>
> - Connection A is setup by user 1 to use transactions.
> - Connection B is setup by user 2 not to use transactions.
> - Connection A is reused by user 2, who thinks he doesn't need
> transactions, but connection A actually requires a commit to work because
> of user 1's previous setting...
>
> People using Interbase have reported this problem also.
>
> Regards, john


--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]



-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to