ID:               33772
 Updated by:       [EMAIL PROTECTED]
 Reported By:      msipria at suomi24 dot fi
-Status:           Critical
+Status:           Open
-Bug Type:         Class/Object related
+Bug Type:         Documentation problem
 Operating System: *
 PHP Version:      5CVS-2005-07-19
 New Comment:

Reclassified as documentation issue.



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

[2005-08-09 14:55:03] [EMAIL PROTECTED]

This patch fixes this problem by doing php_session_flush() before any
__destruct()'s are called:

  http://www.php.net/~jani/patches/bug33772.patch

Note: It won't work if you have compiled ext/session as shared. We need
a better solution, I'm submitting this just  as as temporary one.


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

[2005-08-09 14:01:49] [EMAIL PROTECTED]

This is chicken/egg problem and it cannot be solved. One expect that
destructors are called before session close the other uses object for
save handlers.

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

[2005-07-21 16:38:11] msipria at suomi24 dot fi

my class isn't extension of mysqli class, it just use it as object, and
with real class i have tryed session_write_close() function but mysql
connection is deat, i don't wanna restor it, i just wanna that it will
be alive at the end like now.

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

[2005-07-21 00:10:05] toma at smartsemantics dot com

Adding session_write_close() to the __destruct() function will restore
the write, close, and destroy functions to their proper order.

I use a custom session handler that extends my custom mysqli class.  It
automatically checks for lost database connections and attempts
reconnects, etc.

This is still a bug, but the following makes your custom session
handler viable.

public function __destruct(){
        @session_write_close();
}

Without session_write_close:
starting session
connecting to database
destroying session
writing session
can't write, database connection does not exist
connecting to database
writing session
closing session

With session_write_close:
starting session
connecting to database
writing session
closing session
destroying session

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

[2005-07-19 21:20:45] [EMAIL PROTECTED]

I need this fixed too, it's not possible to use e.g. mysqli as save
handler otherwise..


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

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/33772

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

Reply via email to