Multiple database + pconnect issues

[eluser]Seppo[/eluser]
Oh, you lost me here...

[quote author="Nanodeath" date="1203661009"]The only 1:1 choice for serialization is a multi-dimensional array (which I prefer just as a matter of personal preference), but as far as I can tell either you have the inconvenience of a method call or the inconvenience of multiple levels of indirection.[/quote] No idea what you mean... why multidimensional? why not as I put before?

[quote author="Nanodeath" date="1203661009"]I see what you mean about the extra parameters things now -- you can't force a new persistent mysql connection. But the next question is...does it matter? If you look at db_pconnect in the CI postgre driver, you can't force a new connection (..yet). Same for ms sql. So perhaps just storing the particular database with respect to a particular combination of parameters would be enough...[/quote]Why can't force a new connection? Yes, we can... that's the point, if a new connection is made, there is no reason to switch database on each query...

[quote author="Nanodeath" date="1203661009"]The last question is...what if the SQL server "goes away" in the middle of a script. Can that happen? Otherwise the connection might get reestablished and the db_select method will still think the old database is selected.[/quote]If the server "goes away" doesn't all the script execution stop? should we worry about this?