in reply to Re: Please suggest the best way .ini or pm
in thread Please suggest the best way .ini or pm

but its huge database, as an automation suit who will configure such big data.... only the one database field which user should know.. rest no need.. Also How can we communicate to the database in .ini files.. database is remote system.
  • Comment on Re^2: Please suggest the best way .ini or pm

Replies are listed 'Best First'.
Re^3: Please suggest the best way .ini or pm
by marinersk (Priest) on Jun 26, 2015 at 06:14 UTC

    Yes, that is a modern additional feature to consider: Store configuration in a database (could even be user-specific!); you could reduce the .inifile to holding the database connection information.

    But I wouldn't hard-code anything in the .pmwithout a very specific and strong argument to do so.

    The benefits of keeping code and data separate is a very, very long list, and I've probably forgotten more reasons that some people will learn. Don't make your people edit .pmfiles just to make a config change. You are likely to live to regret it if you do.  :-)

Re^3: Please suggest the best way .ini or pm
by marinersk (Priest) on Jun 26, 2015 at 06:53 UTC

    Side note (and I really am just trying to be helpful, not demeaning in any way): A suit (sort of rhymes with "soot") is something you wear, or one of a family of cards in a deck of cards. I guess it can also be a legal action designed to seek compensation for perceived wrongs.

    A suite (rhymes with "sweet") is a group of things tied together; a suite at a hotel is comprised of adjoining rooms, and a test suite is a bunch of tests that are grouped together as a (generally functional) block.