There's really no other way to do it... You can't serialize a connection or resultset since they are both resources...
If you really wanted you could turn a recordset into an array and store that as a serialised object and pass it around... but a) Depending on how much data a recordset returned it could be quite a slowdown on page viewing. b) It could be a security breach in case there was data int he recordset you never show to the public btu you need for calculations. c) Changes made to the database since the last retrieval would not display. A server is meant to store and serve data.. There really is no other way about it =). Josh. On February 12, 2003 01:52 pm, Lucas Lain wrote: > i will use it for the moment but i was thinking in a "light" solution > ... i dont like the idea of creating a temp table for each page... > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
