I wonder, is there a XOOPS page which closes the db connection after it's finished with grabbing data from db? (while not using the persistent connection)

I may be wrong, but I couldn't find one single "close" line anywhere in the code... am I missing something?

How about putting such thing e.g. in footer, it might solve lot problems with things like this:

Error [Xoops]: Unable to connect to database in file class/database/databasefactory.php line 34

It's an idea, which I got after talking about the error with some folks from czech XOOPS comunity and few web-providers...

I don't wanna be rude but the relevant FAQ is really useless, (No ofense, Mith )

Comments? Reactions?

Error [Xoops]: Unable to connect to database in file class/database/databasefactory.php line 34

This error only shows when the connection can't be made. So far, I have only seen this error when the database was down for some reason, not because the maximum number of connections allowed was reached. So I'm curious as to what the discussion you had in the czech community and the hosters was about...

Herko

The discussion was about our php applications and their db connection closings, which was the theory of some of the hosters.

On the other hand, I came to conclusion, that the error is really only about uncapability to connect to db (because the db is just not accessible due it's down etc.) Our db-server had lil down-time and some other severs had the similar syptoms...

I could say that this morning I didn't wake up with the right foot, the morning post was with too hot head (from the discussions), which is usually not my way of reaction... now I feel lil stupid. I am pulling back the word USELESS off... it's fine. Sorry.


Anyway, why isn't the XOOPS closing his connections to db? any particular reason?