#18158 [Fbk->NoF]: sybase session storage causing data corruption

ID: 18158 Updated by: sniper@php.net Reported By: g.hort@unsw.edu.au -Status: Feedback +Status: No Feedback Bug Type: Sybase-ct (ctlib) related Operating System: Solaris 8 PHP Version: 4.2.1 New Comment: No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to "Open". Thank you. Previous Comments: ------------------------------------------------------------------------ [2002-10-09 10:50:03] iliaa@php.net Please try using this CVS snapshot: http://snaps.php.net/php4-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-latest.zip ------------------------------------------------------------------------ [2002-09-25 06:33:13] sas@php.net Not session related, reclassified. ------------------------------------------------------------------------ [2002-07-19 05:38:28] g.hort@unsw.edu.au I think this is a different problem. This is related to sybase returning an error like already exists when doing an insert and it doesn't occur with mysql and has nothing to do with the size of the session. The corruption occurs in a non-session variable and there doesn't appear to be anything wrong with the session data itself. In 18404, as far as I can see, the database doesn't give an error, the problem occurs with both sybase and mysql and it seems to depend on the size of the session and the session variable becomes undefined. It still occurs with the workaround for this bug in place. However if you still think its the same bug then of course I accept that. ------------------------------------------------------------------------ [2002-07-19 04:57:50] sniper@php.net In the other report (#18404) you said mysql does NOT work.. please, only ONE report per bug. ------------------------------------------------------------------------ [2002-07-19 04:06:02] g.hort@unsw.edu.au As workaround I modified the read routine of the session handler to set a global variable to say whether the session exists. The write routine tests this var to tell whether to do an insert or an update, no errors are returned and everything works fine. see http://sporty.nun.unsw.edu.au/pear_session2.phps. ------------------------------------------------------------------------ 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/18158 -- Edit this bug report at http://bugs.php.net/?id=18158&edit=1