Re: I think I found the ODBC/Solid failures

On Thu, 21 Jan 1999, Andreas Karajannis wrote: > The result set may be empty (e.g. a select returned no rows), > but still you executed some SQL statement. > The function in question (SQLTransact()) was only > introduced to be called on freeing a result since Solid > considers all statements (including selects) as transactions. > So if you don't commit your select before freeing a result, > you will get locking errors on the following statements. Okay, that too might be a problem. I did not realize there was an ordering between odbc_commit and odbc_free_result(). I'll look at the script again to see what I do. > This was especially weird with pconnections. I am running pconnects. > I would consider SQLTransact() coredumping when there is > no transaction pending as a library bug ;-) > Nevertheless, I'll have a lock what could be done here. Once again, thanks to all. -- Michael -- PHP Development Mailing List http://www.php.net/ To unsubscribe send an empty message to php-dev-unsubscribe@lists.php.net For help: php-dev-help@lists.php.net