in reply to mysql, locked databases, Apache::DBI and mod_perl

Bah, I don't know why you're complaining about this, like you said, it just developed a random feature. ;-)

In any case, this sounds like it might be a trap with mod_perl. Take a look at the beginning of this, which talks about general situations (and solutions and debugging techniques) where stuff works and doesn't work apparently at random.

  • Comment on Re: mysql, locked databases, Apache::DBI and mod_perl

Replies are listed 'Best First'.
Re: Re: mysql, locked databases, Apache::DBI and mod_perl
by Flame (Deacon) on May 19, 2003 at 02:49 UTC
    Hmm, I've seen it before, but it does remind me of one other thing I changed... I had a variable that was 'my' previously, and I changed it to 'our' in the hopes that a sub I couldn't conveniently pass it to would be able to get it... I'll change that back and see what happens.

    This is when you wish you had CVS or one of those other systems...


    My code doesn't have bugs, it just develops random features.

    Flame ~ Lead Programmer: GMS (DOWN) | GMS (DOWN)

[reply]
      This is when you wish you had CVS or one of those other systems...

      Stop Wishing. Install (or learn to use) CVS (or the equivalent) ASAP. Without some type of source-code control, you're working without a safety net. The ability to ask "what changed?" questions--and get authoratative answers--can be a huge win when you find yourself in a situation like the one you're in now.

[reply]
        I've tried several times to get it working on my system, and although I have access to CVS via SourceForge, I still haven't been able to figure out how it works... unfortunately.


        My code doesn't have bugs, it just develops random features.

        Flame ~ Lead Programmer: GMS (DOWN) | GMS (DOWN)

[reply]

In Section Seekers of Perl Wisdom