Guest_imported
New member
- Jan 1, 1970
- 0
Hi everybody,
I'm writing my first database client.
This database will be used by about 50 Users.
I will try to do it with Visual C++ 6.0 - ODBC - and direkt SQL commands to a MySQL database.
What I was wondering about is:
Is it more usefull to open a database connection for the whole time the client becomes used, so that I will get a lot of connections during a long time ( maybe the whole day ) to my database !
Or would an expert say: "No, that's not usefull, release the connection after 10 minutes, if the user does not work with it."
On one hand I've got a lot of connections, on the other I get a bunch of connection requests and releases.
So how would a database expert handle this problem ???
Thanks for all answers ( and sorry for my bad english ),
SAM
I'm writing my first database client.
This database will be used by about 50 Users.
I will try to do it with Visual C++ 6.0 - ODBC - and direkt SQL commands to a MySQL database.
What I was wondering about is:
Is it more usefull to open a database connection for the whole time the client becomes used, so that I will get a lot of connections during a long time ( maybe the whole day ) to my database !
Or would an expert say: "No, that's not usefull, release the connection after 10 minutes, if the user does not work with it."
On one hand I've got a lot of connections, on the other I get a bunch of connection requests and releases.
So how would a database expert handle this problem ???
Thanks for all answers ( and sorry for my bad english ),
SAM