|
php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login |
PatchesPull RequestsHistoryAllCommentsChangesGit/SVN commits
[2004-04-13 12:34 UTC] sniper@php.net
[2004-04-13 17:39 UTC] michaels at crye-leike dot com
[2004-07-11 18:40 UTC] thekid@php.net
[2004-07-12 18:00 UTC] michaels at crye-leike dot com
[2004-07-12 23:08 UTC] thekid@php.net
[2004-07-16 21:10 UTC] michaels at crye-leike dot com
|
|||||||||||||||||||||||||||||||||||||
Copyright © 2001-2025 The PHP GroupAll rights reserved. |
Last updated: Sun Oct 26 23:00:02 2025 UTC |
Description: ------------ Using FreeTDS 0.62.1 compiled with: ./configure --with-tdsver=4.2 --enable-msdblib --with-gnu-ld --enable-shared --enable-static Using PHP 4.3.5 compiled with: ./configure --with-mysql=/usr/local/mysql/ --enable-track-vars --enable-trans-sid --with-sybase-ct=/usr/local/ --with-pgsql=/usr/local/pgsql/ --enable-xslt --with-xslt-sablot --with-zlib --with-ldap --with-apxs=/usr/local/apache/bin/apxs Using TDS version 7.0 Using Microsoft SQL Server 7.0 It seems that sybase_query() triggers an E_NOTICE ("Sybase: Unexpected results, cancelling current") whenever the query in question is a stored procedure. This notice is not triggered when using either "--with-sybase" or "--with-mssql" (using dblib). For those of us running with an error_reporting level of E_ALL, this causes a problem, as we'd either have to preface every call to sybase_query() with "@" and handle all Sybase errors manually, or lower the error_reporting level. Reproduce code: --------------- <? $dbh = sybase_connect('db_host', 'user', 'pass'); sybase_select_db('db_name', $dbh); sybase_query(" create procedure test_bug as begin select 1 end ", $dbh); sybase_query("exec test_bug", $dbh); sybase_query("drop procedure test_bug", $dbh); ?> Expected result: ---------------- Expected empty output with no notices triggered. Actual result: -------------- Notice: sybase_query(): Sybase: Unexpected results, cancelling current in - on line 13