ID: 40681
User updated by: frmi at freemail dot hu
Reported By: frmi at freemail dot hu
Status: Bogus
Bug Type: *Database Functions
Operating System: linux
PHP Version: 5.2.1
New Comment:
OK.
I see I'll have no success with you.
But you are surely wrong.
The base concept is ok, but it is a little confusing.
If there is pconnect, then there should be pclose.
No place to doubt.
If the concept is sooooo persistent as you say,
and really there must be no pclose, then there must be no pconnect.
I could understand this as well.
Then the connection could be a configured one and it would be opened
when trying to use it, or at script startup.
But I think this would be topo strong.
I cannot understand why a pclose would destroy concept of persistency.
It is simply not true.
And the problem is, that with denying a small bit of code to complete
the concept, there are lots of problems which cannot be handled.
Previous Comments:
------------------------------------------------------------------------
[2007-03-01 19:47:51] [EMAIL PROTECTED]
>Even the documentation says that starting from the version 1.1
>oci_close() correctly closes the Oracle connection.
>Not mentioning that it is not true for persistent connection.
All persistent connections are not affected by *_close() functions,
it's not something OCI8 specific.
MySQL persistent connections cannot be closed by mysql_close() etc.
etc.
PHP behaves this way since the very introduction of persistent
connections, and I doubt this is a subject to change in the future,
since it'd destroy whole concept of "persistency".
Hence the status of the report.
------------------------------------------------------------------------
[2007-03-01 19:38:29] frmi at freemail dot hu
It's unfriendly to set status to bogus without having reason for that.
Even the documentation says that starting from the version 1.1
oci_close() correctly closes the Oracle connection.
Not mentioning that it is not true for persistent connection.
Please be collaborative.
------------------------------------------------------------------------
[2007-03-01 19:22:20] frmi at freemail dot hu
>I believe you're fixing wrong problem.
>You should fix mystic behaviour of oracle first.
Face what?
Good joke.
Easy to say that instead of telling a solution.
I've such experience, even solved bug in oracle software just surfing
source code, but at first waiting few months for the solution from
oracle support.
I think oci_pclose would be good, no reason of not having that.
And it is a bit easier then solving all oracle bugs.
------------------------------------------------------------------------
[2007-03-01 18:30:19] [EMAIL PROTECTED]
>Persistent connection is a choice for enabling a better performance.
>Eg. keepalive in http. It should not disable the right to disconnect
at will.
Well, face it then.
I believe you're fixing wrong problem.
You should fix mystic behaviour of oracle first.
------------------------------------------------------------------------
[2007-03-01 18:09:34] frmi at freemail dot hu
>>In some cases I want to close the connection and reconnect.
>Could you please elaborate? What kind of cases?
Sure.
Eg. some mystic behaviour of oracle or the developed system, which can
be resolved by simple reconnect, until bug is found and resolved. It
happens that it is needed.
>>what to do, when it must be closed?
>One of the reason why persistent connections are called "persistent"
is that you cannot close them.
>So if you really need to close the connection and reopen it (I can't
imagine why) - don't use persistent connections or restart Apache.
I cannot belive that. Persistent connection is a choice for enabling a
better performance. Eg. keepalive in http. It should not disable the
right to disconnect at will.
I think closing the user app is users choice, closing or freeing apps
sessions or variables is developers choice.
Restarting apache disturbs other users, while disconnecting just one
user doesn't.
I can understand if you say that oci_close must not disconnect the
session, but then a oci_pclose would be nice.
------------------------------------------------------------------------
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/40681
--
Edit this bug report at http://bugs.php.net/?id=40681&edit=1
