in reply to Re: What if mod_perl is not an option?
in thread What if mod_perl is not an option?

Sorry, but I don not understand what's wrong with Perl/CGI that needs to be replaced by postgres (PostgreSQL). Perl/CGI is a way to make dynamic web-pages and postgres is a database. The one cannot replace the other, they have to work together. Or am I missing something subtle here?

CountZero

"If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law

  • Comment on Re: Re: What if mod_perl is not an option?

Replies are listed 'Best First'.
Re: Re: Re: What if mod_perl is not an option?
by borisz (Canon) on Feb 04, 2004 at 14:28 UTC
    Perl/CGI is a way to make dynamic web-pages and postgres is a database. The one cannot replace the other, they have to work together. Or am I missing something subtle here?
    Yes, I suggest to use postgres with mod_perl. If this is really, really, really not possible, stay with CGI and mysql.
    Boris
      Without trying to derail this thread (which is more to do with CGI versus mod_perl rather than MySQL), you still haven't really explained why he should also switch to postgres. Is there a specific reason why he shouldn't continue on using MySQL, even with mod_perl (assuming he had the option)?
        No, there is no reason for _must_ use postgres, MySQL is also a database. But in my opinion postgres is much richer and robust than MySQL. Now as the question is CGI/Mod_perl with mysql why not get familar with the very good database postgres? That saves that switch next year.
        Boris