From: | Dustin Sallings <dustin(at)spy(dot)net> |
---|---|
To: | M(dot)Boekhold(at)et(dot)tudelft(dot)nl |
Cc: | "Shawn T(dot) Walker" <swalker(at)iac(dot)net>, Chris Hardie <chris(at)summersault(dot)com>, M(dot)Boekhold(at)ITS(dot)TUDelft(dot)NL, pgsql-general(at)postgreSQL(dot)org |
Subject: | Re: [GENERAL] Postgres CGI Security Problem |
Date: | 1998-08-09 19:51:50 |
Message-ID: | ML-3.5-SPY.902692310.6838.dustin@bleu.west.spy.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> > Chris Hardie writes:
> > > In anycase, I'm using the Postgres.pm module with PERL, and it doesn't
> > > seem to support the passing of a username/password pair (correct me if
> > > I'm wrong) from a CGI script. I'll attempt to code that, unless
> > > someone has done it already.
>
> Actually Pg.pm *does* allow you to connect with a username/password. If
> you use the 'new-style' methods of Pg.pm, do $db->connect("dbname=..
> user=.. password=..");. If you use the 'old-style' (like I do), use
> PQconnectdb() with the same arguments.
He said Postgres.pm, not Pg.pm. There are three modules (that I've
used anyway) to do Postgres connectivity via perl:
Pg.pm (ugly, too C like for perl)
Postgres.pm (very perl like)
DBD::Pg (best way to go, very similar to Postgres.pm)
--
SA, software.net My girlfriend asked me which one I like better.
pub 1024/3CAE01D5 1994/11/03 Dustin Sallings <dustin(at)spy(dot)net>
| Key fingerprint = 87 02 57 08 02 D0 DA D6 C8 0F 3E 65 51 98 D8 BE
L_______________________ I hope the answer won't upset her. ____________
From | Date | Subject | |
---|---|---|---|
Next Message | Paul Ramsey | 1998-08-10 02:27:44 | Postgres && GIS |
Previous Message | Sferacarta Software | 1998-08-09 13:12:49 | Re: [GENERAL] CREATE TABLE ... CONSTRAINT |