in reply to Re^3: Moose::Role to provide DBI interface
in thread Moose::Role to provide DBI interface

As mentioned in OP, I'm trying to ensure there is nothing technically wrong with setting up a new DB handler when switching to a new database. Since I'm not an expert on the underpinnings of OO and DBI, I'm worried there might be some kind of weird interaction that I might be missing. Maybe this might create database connections that never die, for example. I just don't know. I've come to learn that I'll often go down paths that lead to trouble. The benefit is I learn a lesson, but at the expense of a lot of time lost. I'm just trying to avoid that pain. I also enjoy seeing ideas from other Monks on my code. I always learn something new when I post here like the suggestion to use a config file above, which I hadn't thought of. I'm a hobbyist. But if you want to take me under your wing and turn me into a programming guru, let me know.

$PM = "Perl Monk's";
$MCF = "Most Clueless Friar Abbot Bishop Pontiff Deacon Curate";
$nysus = $PM . ' ' . $MCF;
Click here if you love Perl Monks

  • Comment on Re^4: Moose::Role to provide DBI interface

Replies are listed 'Best First'.
Re^5: Moose::Role to provide DBI interface
by Anonymous Monk on Feb 08, 2017 at 21:38 UTC
    "I'm trying to ensure there is nothing technically wrong with setting up a new DB handler when switching to a new database."

    This statement shows that you really don't understand the role of a Relational Database, much less how to interface with Perl. Please stop telling us HOW you want to do stuff and just tell us WHAT you are trying to do.

[reply]

      To the contrary, I've cobbled together functional programs with mysql and have used DBI in the past. In fact, I've worked fairly extensively with databases and basic web development. I've read good chunks of books on databases 20 years ago. But it's not something I use everyday or need to use everyday and anything I learn quickly dissipates until 6 months or a couple years later when I want to work on a project I'm interested in.

      Again, I'm not a full-time, professional programmer. I'm not even a part-time programmer. I'm barely an enthusiast. I could avoid making amateurish mistakes by becoming a professional programmer, but that's not my objective. Yup, I am pretty clueless on many things and have only vague ideas on what goes on under the hood. I know enough to be dangerous. I also know enough to get a sense that what I'm doing doesn't quite feel right but I'm not sure what other better, alternative approaches might exist. That's why I appreciate the feedback I get here. I always learn a lot at PerlMonks.

      My sole objective is to become as efficient as possible at writing my own programs for my own use that I'm happy with and ones that I don't have to abandon because they are spaghetti code or bug ridden and that aren't too tedious or confusing to write and maintain. And I get a good amount of pleasure encountering the many puzzles programming presents and figuring them out. That's good enough for me.

      Thanks for the feedback. Have a good day, bud.

      $PM = "Perl Monk's";
      $MCF = "Most Clueless Friar Abbot Bishop Pontiff Deacon Curate";
      $nysus = $PM . ' ' . $MCF;
      Click here if you love Perl Monks

[reply]

In Section Seekers of Perl Wisdom