#20861 [Com]: sybase_query fail to handle stored procedure result with "nocount" option

ID: 20861 Comment by: steil at zweitwerk dot com Reported By: csollet at coleebris dot com Status: Closed Bug Type: Sybase-ct (ctlib) related Operating System: Linux PHP Version: 4.3.0RC2 Assigned To: thekid New Comment: Bug #20861 seems to be closed since supposed to be bogus if I understand things correctly. I found the same bug and don't believe it being bogus. My example (Sybase 11.7, Linux, PHP4.3.1) arose when trying to call sybase' build-in procedure sp_pkeys, i.e. $db = sybase_connect("host", "user", "pass"); $query = sybase_query('sp_pkeys some_table', $db); var_dump(sybase_fetch_array($query)); This results in "bool(false)". A closer look at the procedure's body shows that it 'set nocount on'. Recompiling the procedure without this line gives the expected result, e.g. array(10) { [0]=> string(11) "jadisnetHUM" ["table_qualifier"]=> string(11) "jadisnetHUM" [1]=> string(3) "dbo" ["table_owner"]=> string(3) "dbo" [2]=> string(5) "asset" ["table_name"]=> string(5) "asset" [3]=> string(7) "assetid" ["column_name"]=> string(7) "assetid" [4]=> string(1) "1" ["key_seq"]=> string(1) "1" } I strongly suspect PHP is looking for the rowcount before trying to retrieve data and therefore is mislead by 'nocount on'. I also called both, original and without 'nocount on', versions of the procedure with a different programming language (Omnis) and encountered no problems in either case. Therefore it should be possible to correct PHP's fetching routine to not relying on not setting 'nocount on'. I would expect at least to be able to excute build-in procedures without problems, i.e. 'set nocount on' seems not to be that special as a former submitter suggested. Previous Comments: ------------------------------------------------------------------------ [2002-12-10 05:11:16] thekid@php.net ------ Feedback from original reporter ------ Timm Friebe wrote: [...] > Thanks - I've updated the bug. What do you think? > Should I remove the notice? Hum, after getting a closer look at the problem, i've realized that i've been fooled by another new features of PHP4.3 that breaks our apps a bit later : Dispite new sybase notice, i got expected result as you wrote it in #20861 (not what i figured out at first look). So #20861 is boggus. Sorry for the false alarm. About the notice itself, i haven't, personaly, any requirement since, except for debuging purpose, all our sybase_query are @ prefixed (don't want any sql print out to users in case of errors). Maybe PHP4.3 should be shipped with a "BC changes" file that stat this one? Regards, Christophe. ------------------------------------------------------------------------ [2002-12-07 13:51:51] thekid@php.net <?php /* Script to reproduce bug #20861 * * $Id$ */ ini_set('sybct.min_server_severity', 11); $db= sybase_connect('gurke', '******', '******'); sybase_select_db('tempdb', $db); // var_dump(sybase_query(' // create procedure test_bug // @input int // AS // BEGIN // set nocount on // // select @input 'result' // return 2 // END // ', $db)); // This doesn't print out the error message $q= sybase_query('test_bug 1', $db); while ($data= sybase_fetch_object($q)) { var_dump($q, $data); } // This actually prints out the warning message as // we have two resultsets $q= sybase_query(' declare @return int exec @return= test_bug 1 select @return ', $db); while ($data= sybase_fetch_object($q)) { var_dump($q, $data); } // var_dump(sybase_query('drop procedure test_bug', $db)); sybase_close($db); ?> ------------------------------------------------------------------------ [2002-12-07 08:38:54] thekid@php.net Well, in earlier versions sybase_ct silently cancelled the unexpected results, now it will inform you it is doing so - I thought it was nice to be a bit more verbose about things. ------------------------------------------------------------------------ [2002-12-06 10:48:02] csollet at coleebris dot com After some more test, i can get the notice (notice -> no result) without "set nocount on". Don't have pushed further since the procedure involved is about 400 lines with call to others procedures. So, just to add that "set nocount on" is a case, not the only one, that trigger the error. ------------------------------------------------------------------------ [2002-12-06 09:53:00] csollet at coleebris dot com Test script : <? $sy = sybase_pconnect('DBHOST', 'user', 'pass'); sybase_select_db('MyDB', $sy); sybase_query("test_bug 1", $sy); ?> produce : Notice: sybase_query() [http://www.php.net/function.sybase-query]: Sybase: Unexpected results, cancelling current in - on line 4 with test_bug defined as follow : create procedure test_bug @input int AS BEGIN set nocount on select @input 'result' return 2 END Removing the "set nocount on" lead to expected result but, of course, in real wold sp, the nocount option is rarely used for fun... Build with Sybase ctclient v12.5 Works perfectly well with 4.2.3 and previous. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=20861&edit=1