ID:               16704
 Updated by:       [EMAIL PROTECTED]
 Reported By:      [EMAIL PROTECTED]
 Status:           Feedback
 Bug Type:         OCI8 related
 Operating System: Windows 2000
 PHP Version:      4.1.2
 New Comment:

Hi,

I'll send you a nice testsript tomorrow (European Time).

cu


Previous Comments:
------------------------------------------------------------------------

[2002-04-22 14:45:55] [EMAIL PROTECTED]

please send me a shot _selfcontained_ php script that 
shows and explains your problem! 
 

------------------------------------------------------------------------

[2002-04-22 14:06:13] [EMAIL PROTECTED]

I also tried OCINLogon, but there was no difference.

Addition: As the documentation implies: it should be no problem for any
OCI*logon function to make more than one connections!

------------------------------------------------------------------------

[2002-04-22 13:55:31] [EMAIL PROTECTED]

 use OCINlogon to force session isolation. 
 

------------------------------------------------------------------------

[2002-04-22 13:53:13] [EMAIL PROTECTED]

Bah! Bug in bug report:

5.) echo out connection one $con1 -> you get Resource id # 2
                                                    _______^

------------------------------------------------------------------------

[2002-04-22 11:55:47] [EMAIL PROTECTED]

Update:

One piece of information was wrong: I use always the same instance/SID
name. But now I've even tried to create a alias for my instance that
both conns get a different instance without success.

After digging deeper into the problem I've figured out a really easy
way to see the bug:

1.) Create connection one $con1
2.) echo it out echo $con1 -> you get Resource id # 1
3.) Create connection two $con2
4.) echo it out echo $con2 -> you get Resource id # 2
5.) echo out connection one $con1 -> you get Resource id # 1

You see even the connection handles reflect the reality.

cu

------------------------------------------------------------------------

The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
    http://bugs.php.net/16704

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

Reply via email to