I would make the configuration information into a table, or better yet, a configuration file. That way you don't need to fiddle with the module code every time anything changes the database. It also allows you to reuse the module for different applications, but change which configuration file you specify -- that's way better than having to edit the module for each location where you want to use it.

But excellent plan to modularize that aspect of your programming .. modularity is definitely the way to go.