Hmm, okay. Well given that my test returned blank values I guess that confirms your suspicions, right? Any ideas as to why?
Tony -----Original Message----- From: Kristis Makris [mailto:[EMAIL PROTECTED] Sent: Friday, April 20, 2007 1:47 PM To: Day, Tony Cc: [email protected] Subject: RE: [scmbug-users] Bugzilla Not Being Updated On Fri, 2007-04-20 at 13:10 -0600, Day, Tony wrote: > Kristis, > You had me try that yesterday and I reported back that I rec'd back no > values. I tried again and the behavior is the same today. All I get is > $VAR1 = ''; I'm now asking to print the credentials used to connect to the database, not the value received. You may be trying to connect with a blank username/password. > With respect to debugging the DBI module, I think I am just going to > hold off until we upgrade Bugzilla. I am going to be getting Bugzilla > 3.0 going maybe as early as next week. Given that I have already spent > the majority of a week trying to get this going I have to catch up on > some other things next week. And I have Friday Afternoonitus and will > most likely be leaving for the day soon. :) Keep in mind Bugzilla 3.0 is not supported by Scmbug yet. > ## right here, the very first statement > > open OUTFILE, "> C://output.txt"; > print OUTFILE "the db host is: " . Dumper($::db_host); > print OUTFILE "the db port is: " . Dumper($::db_port); > print OUTFILE "the db name is: " . Dumper($::db_name); > print OUTFILE "the db username is: " . Dumper($::db_username); > print OUTFILE "the db password is: " . Dumper($::db_password); > close OUTFILE; > > I want to make sure the connection to the database is initiated > correctly. That we are not running into some case where due to > threading/forking whatever reason these variables remained > uninitialized. > > _______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
