[PHP-DEV] Bug #9906 Updated: Problems with result-set from temporary tables

2001-07-25 Thread andy

ID: 9906
Updated by: andy
Reported By: [EMAIL PROTECTED]
Old Status: Feedback
Status: Closed
Bug Type: Sybase-ct (ctlib) related
Operating System: Linux RedHat 7.0
PHP Version: 4.0.3pl1
New Comment:

no feedback...

Previous Comments:


[2001-06-26 17:07:51] [EMAIL PROTECTED]

Have you tried my example? If so, what results do you
have? It may very well be that I simply didn't create
a complex enough example, or something, but I don't
see a bug, so this'll be closed if you don't have
anything further to add.



[2001-03-22 10:36:57] [EMAIL PROTECTED]

I have a hard time believing that this is a PHP bug.

#1: Try upgrading to a newer release.
#2: Here is what I tried to test your bug:
 create proc phpb
 as
 begin
   create table #phpb (id int, foo varchar(255))
   insert into #phpb values (1, "a")
   insert into #phpb values (1, "a")
   insert into #phpb values (1, "a")
   insert into #phpb values (1, "a")
   insert into #phpb values (1, "a")
   insert into #phpb values (1, "a")
   insert into #phpb values (1, "a")
   insert into #phpb values (1, "a")

select * from #phpb

end

PHP script looks like:


I got the exact same result from both PHP and isql...



[2001-03-21 17:46:07] [EMAIL PROTECTED]

I have some stored procedures that return a result from a temporary table. When via 
ct-lib i try to get the rows it didn´t return anything.
I try with the function sybase_query , and when i get the resource handler none of 
this functions give me any result:
sybase_num_rows, sybase_fetch_array,sybase_fetch_row.

the reproduction is easy just create a stored procedure that create, fill and select a 
temporary table.

if you use the php ct-lib functions they didn´t return any result.







Edit this bug report at http://bugs.php.net/?id=9906&edit=1


-- 
PHP Development Mailing List 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]




[PHP-DEV] Bug #9906 Updated: Problems with result-set from temporary tables

2001-06-27 Thread joey

ID: 9906
Updated by: joey
Reported By: [EMAIL PROTECTED]
Old-Status: Open
Status: Feedback
Bug Type: Sybase-ct (ctlib) related
Operating system: 
PHP Version: 4.0.3pl1
Assigned To: 
Comments:

Have you tried my example? If so, what results do you
have? It may very well be that I simply didn't create
a complex enough example, or something, but I don't
see a bug, so this'll be closed if you don't have
anything further to add.

Previous Comments:
---

[2001-03-22 10:36:57] [EMAIL PROTECTED]
I have a hard time believing that this is a PHP bug.

#1: Try upgrading to a newer release.
#2: Here is what I tried to test your bug:
 create proc phpb
 as
 begin
   create table #phpb (id int, foo varchar(255))
   insert into #phpb values (1, "a")
   insert into #phpb values (1, "a")
   insert into #phpb values (1, "a")
   insert into #phpb values (1, "a")
   insert into #phpb values (1, "a")
   insert into #phpb values (1, "a")
   insert into #phpb values (1, "a")
   insert into #phpb values (1, "a")

select * from #phpb

end

PHP script looks like:


I got the exact same result from both PHP and isql...

---

[2001-03-21 17:46:07] [EMAIL PROTECTED]
I have some stored procedures that return a result from a temporary table. When via 
ct-lib i try to get the rows it didn´t return anything.
I try with the function sybase_query , and when i get the resource handler none of 
this functions give me any result:
sybase_num_rows, sybase_fetch_array,sybase_fetch_row.

the reproduction is easy just create a stored procedure that create, fill and select a 
temporary table.

if you use the php ct-lib functions they didn´t return any result.



---



ATTENTION! Do NOT reply to this email!
To reply, use the web interface found at http://bugs.php.net/?id=9906&edit=2


-- 
PHP Development Mailing List 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]