> > on rereading your post - your storing session data in a db, why bother; > secondly > it sounds like you just overwriting the session record with a new > transaction > id rather than adding a new transaction id [record] and leaving any > already existing > transactions available. > > basically pass the transaction id around when you need to keep referring > to > an existing transactions and maintain a 'stack' of active transactions. > Reason I store session info in 'sessions' table CREATE TABLE `sessions` ( `sessID` varchar(45) NOT NULL default '', `last_update` timestamp(14) NOT NULL, `session_values` text NOT NULL, PRIMARY KEY (`sessID`) ) TYPE=MyISAM; instead in $_SESSIONS (something like $_SESSION['session_info']['User'], $_SESSION['session_info']['UserNo'], $_SESSION['session_info']['OrderID, '], $_SESSION['session_info']['PageID'], etc.) is to be able to see who is "online", eventually by redoing sessions table, when they started session, how much time they spend on application, what they mostly use from application, etc. (requests from "the office"). -afan -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
