Just a quick question regarding having a server that extracts user information from / writes information to a database.
Should I practice:
1) Opening a connection when the server starts, close the connection when the server closes
2) Open a connection only when the database needs to be used (possibly frequently) and close it immediately
I'm not really aware of the raw behind a connection with a SQL database, so I'm not sure of the security consequences etc etc
I would assume 1) is a lot faster also.
Note: If you are offering a suggestion, could you offer it for two different situations: where the database is local to the server and where the database is hosted online?
Thanks yy0y0y0 xoxoxo
Should I practice:
1) Opening a connection when the server starts, close the connection when the server closes
2) Open a connection only when the database needs to be used (possibly frequently) and close it immediately
I'm not really aware of the raw behind a connection with a SQL database, so I'm not sure of the security consequences etc etc
I would assume 1) is a lot faster also.
Note: If you are offering a suggestion, could you offer it for two different situations: where the database is local to the server and where the database is hosted online?
Thanks yy0y0y0 xoxoxo


).
The only problem is, the only way I actually learned what I know now was through already made engines. I would then tinker with variables and functions until I knew what they did to the engine, then rewrite the engine myself seeing if what I knew worked. My understanding is C++ is so ridiculous that I probably have zero hope of learning it using the same method, so
Anywho I know zero percent about C++, so I doubt I'd be able to offer much assistance, but I suppose if somebody wrote the system the least I could do is port(script, don't hurt me) it into EML(E++, whatever you guys are calling it