RE: [misterhouse-users] mh and mySQL

[Bruce W. <br...@mi...>]

>  I have done this change, the code is now:
>
>     use DBI;
>     print "Start\n";
>     my ($dbh) = DBI->connect("DBI:mysql:APRSstat", "mh", "mhpwd") or print
> "Error in DBI connect: $!\n";
>     print "Connected\n";
> ...
>  Here is what I get:
>
>          suse: # ./mh -run /home/mhrb/code/testmysql.pl
>
>          Running: /home/mhrb/code/testmysql.pl
>          Start
>
>          Done running: /home/mhrb/code/testmysql.pl
>          suse: #
>
>  As you can see no error at all. perl
> /home/mhrb/code/testmysql.pl is still

Well hmmmmm.   I'm stumpped.  Something bad must have happened in that
connect in order not to get either the error print or this subsequent error
message in mh:

      do "$pgm";
      print "Error with $pgm: $@\n" if $@;

Do you have the same problem with you run a DBI connect in your mh user
code?   Does it cause mh to stop?

I assume you are running the stand alone .pl code with 'mh -run test.pl' as
debug, or is there any reason or advantage to that over a simple 'perl
test.pl'?   The 'mh -run xyz.pl' method is useful for those who do not have
perl installed (using mh.exe) or want to use a mh module without bothering
with adding mh libs to their INC path.

Bruce