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

 ID:                 24252
 Updated by:         [email protected]
 Reported by:        jpenn at cheetah-soft dot com
 Summary:            Problem with session_set_save_handler() when
                     connecting to db outside of obj
-Status:             Open
+Status:             Bogus
 Type:               Feature/Change Request
-Package:            Feature/Change Request
+Package:            *General Issues
 Operating System:   RHAT 7
 PHP Version:        4.3.1
 Block user comment: N
 Private report:     N

 New Comment:

This can't be done in another way. There are multiple factors affecting
this. For instance session.auto-start might start a session before the
actual script runs. Then there's the whole shutdown order chicken and
egg problem: what should be shutdown first - global variables or
sessions? - If sessions first: What happens to destructors trying to
access sessions. if variables first - well, you see it, the session
can't access the connection.


Previous Comments:
------------------------------------------------------------------------
[2003-09-14 23:14:31] jpenn at cheetah-soft dot com

Anyone know what the actuall status of this is. I see that the category
was changed to 'feature request', not really sure why.



Is this an internal problem with ZE1?



~ Thanks

------------------------------------------------------------------------
[2003-07-09 11:09:20] jpenn at cheetah-soft dot com

sniper - sorry for the personal insults, no harm meant. Problem is, what
you just explained as 'full but short' - that is exactly what was posted
- without the opening and closing php tags.



Problem is you can't cut and paste this code as it will not work. If you
are testing this you will need the entire class to do the testing as
without all six (6) of the arg's, the session_set_save_handler() will
not work at all. So, to get what this bug is, you will need the class
itself, which can be found at this address:
http://www.cheetah-soft.com/csh/



Download the class and set up something temporary for it. Once you have
the class as downloaded, it will run fine.



After you have it running, move the db connection outside of the class
and you will see the bug.



Thanks

------------------------------------------------------------------------
[2003-07-09 10:55:53] [email protected]

Please leave the personal insults out.

You still don't seem to understand what "full but short" script means so
I'll try and explain it simply:



1. It starts with <?php and ends with ?>

2. I can copy'n'paste it from this report to a file and run

without having to edit it / add to it

3. It contains ONLY the necessary lines which show the problem



Clear now?



------------------------------------------------------------------------
[2003-07-09 10:51:05] jpenn at cheetah-soft dot com

What do you want sniper. Do you want the whole 300 lines of code from
the session handler?

------------------------------------------------------------------------
[2003-07-09 10:40:03] jpenn at cheetah-soft dot com

[quote]

As long as you fail to provide a full, but short example script which

CLEARLY shows whatta hell you're talking about, this stays bogus.

[/quote]

What in gods name are you talking about? Do you not see in the 4th post
on this bug? That is as clear as it gets. Are you a kid or something
sniper? This is rediculous that you are popping in and out of this and
totally overlooking the posts on this bug.



[From 4th post in this bug]

session_set_save_handler( array( &$this, 'open' ), array( &$this,

'close' ), array( &$this, 'read' ), array( &$this, 'write' ), array(

&$this, 'destroy' ), array( &$this, 'gc' ) );



Now, this is the open method:



function open( $blah, $blah )

{

      $res = mysql_connect( 'blah', 'blah', 'blah' );

      mysql_select_db( 'blah', $res );

      return( true );

}

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



Do you not see that? Do you want it emailed to you?

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


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/bug.php?id=24252


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

Reply via email to