Re: Mojolicious and connection to a database

[trippledubs]

looks great. Conditionally loading a config. Might be able to make it more resilient by making sure what you think is there, like "/inc/script/my_lib.conf". You are checking $ENV{PAR_TEMP} to see if it's set, but not checking to see if it's set correctly. Is the file there? Does it have all the data you need? Does it bomb out correctly when somethings wrong? Assume that something will go wrong, now how long is it going to take to find out why with the default error messages?

Break it imaginatively and just kinda see what happens.

[frazap]

Well, loading the config file that way is to make sure the app works when packed with pp. It's no big deal once it's tested.

My question was more in relation with remembering the connection done using the hash.

Could the connection be broken by the database server when the page has been load ? If yes, can I check this rather then using the hash value ?

Thanks for helping anyway !

[bliako]

What if your database server crashes/shuts down/restarts after you run the plugin() to connect to it? %connections flag will not tell you that. In general, one can ping() prior to, or eval() on each db operation and catch the error if any. So perhaps convert this flag to a sub which pings the db-handle you think you have and return the result. See check if DBI is still connected.

[trippledubs]

hmm.. maybe try testing by putting a load on the web server and see how many connections you have to the database? I would think if that part is not working right you would see either increasing number of connections to the database up to some ceiling or your pages not getting data from the database. If I understand your concern correctly.