ID: 22986 Comment by: why at email dot address dot com Reported By: ray at unreal64 dot net Status: Open Bug Type: ODBC related Operating System: Windows NT4.0 PHP Version: 4CVS-2003-03-31 (stable) New Comment:
Pgsql solves this trouble by 'connection flags' and PGSQL_CONNECT_FORCE_NEW. Previous Comments: ------------------------------------------------------------------------ [2003-03-31 11:51:22] ray at unreal64 dot net Hi ! ODBC function "odbc_do_connect" caches connection. It setup "hashed_details" variable and tries to reuse physical DB connection if new PHP connection is being created. It brings BIG problem while creating more complicated things. Imagine, you have some long server side action over database running in transaction (allready get point ? :) Thin client need to show procedure progress. Details are not important, but client 'shows' progress bar. So, inside 'big' server side action, need to be updated 'progress' table which is used by another HTTP request to show real progress to user (action can take tenths seconds). So, if I need to open 2 separate connections, I am in the trouble. Ofcourse, the same user, the same password, the same cursor type. I think it is ugly to create separate user do to this :) [even it is temporary solcution ofcourse] So, I suggest to add parameter to PHP's odbc_connect/pconnect - something like "I am not soo stupid as I look and I really need 2 connections" or add 'flag' to 'cursor type' (and declare this last parameter as 'connection flags' rather 'cursor type') - something like SQL_FLG_NO_CONN_CACHE. Would be nice feature :) If it is 'someway' possible, please, let me know. I didn't find how. Thank you, Have a niceday Ray ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=22986&edit=1
