If you have multiple users for your db, you will not want persistent
connections because there's a limit to how many simultaneous connections you
can have to a MySQL db.
On Feb 14, 2011, at 3:08 PM, Paul Dupuis wrote:
> Björnke,
>
> In other languages, in days gone by, it was good practice to
It is my experience that when connecting to web based SQL servers, that they
drop you themselves after a period of idle time. This is of course, to prevent
someone from running a kind of DDOS on your SQL server.
Unless you control the server, you cannot disable this. I agree with the
assessmen
Björnke,
In other languages, in days gone by, it was good practice to keep the
connection open if an application expected to issue multiple queries
(such as a user driven reporting application) becuase there was overhead
in setting up a connection and creating and opening a connection,
execut
I'm not a experienced sql - lc connection maker either, but i ask myself why to
keep a connection alive? So I take the freedom to append my own question to
yours:
Some people like to keep alive their DB connections. But isn't it usually a
more robust approach to close the connection as soon as
I can think a few way to construct a "keep-alive" process to ensure that
a connection to a MySQL database via the LiveCode database drivers
doesn't time out. However, it occurs to me that folks who spend more
time writing LiveCode MySQL applications than I may have come up with a
"best" way to
