Mailing List Archive: [Bricolage-General] Re: [Bricolage-Bugs] [Bug 287] Our SQL Parsing is Bogus

[Bricolage-General] Re: [Bricolage-Bugs] [Bug 287] Our SQL Parsing is Bogus

Jan 16, 2003, 11:13 PM

Post #1 of 8 (1306 views)

Moving this to Bricolage-General, a better place for questions.

On Thursday, January 16, 2003, at 04:16 PM,
bugzilla-daemon@thepirtgroup.com wrote:

> ------- Additional Comments From sszabo@bigpanda.com 2003-01-17 00:16
> -------
> Can you use either the PGPASSWORD environment or the pgpassfile (for
> 7.3)
> functionality?
>
> http://bugzilla.bricolage.cc/show_bug.cgi?id=287

Uh, no. The password goes into bricolage.conf. If you leave it blank,
it'll default to "nalletsac" in Bric::Config. I could probably change
that, though, to check for PGPASSWORD, first. Then you'd just have to
add

PerlPassEnv PGPASSWORD

To your httpd.conf. Thoughts, people? If I do this, then Bric::Config
should probably also check for other relevant DBI and PostgreSQL
constants...or maybe just DBI constants, since really we should sort-of
maintain cross-database compatibility (not that anyone has ported
Bricolage to MySQL yet).

Regards,

David

--
David Wheeler AIM: dwTheory
david@wheeler.net ICQ: 15726394
http://david.wheeler.net/ Yahoo!: dew7e
Jabber: Theory@jabber.org

-------------------------------------------------------
This SF.NET email is sponsored by: Thawte.com
Understand how to protect your customers personal information by implementing
SSL on your Apache Web Server. Click here to get our FREE Thawte Apache
Guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0029en
_______________________________________________
Bricolage-General mailing list
Bricolage-General@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bricolage-general

[Bricolage-General] Re: [Bricolage-Bugs] [Bug 287] Our SQL Parsing is Bogus [ In reply to ]

sszabo at megazone23

Jan 17, 2003, 8:00 AM

Post #2 of 8 (1296 views)

Permalink

On Thu, 16 Jan 2003, David Wheeler wrote:

> On Thursday, January 16, 2003, at 04:16 PM,
> bugzilla-daemon@thepirtgroup.com wrote:
>
> > ------- Additional Comments From sszabo@bigpanda.com 2003-01-17 00:16
> > -------
> > Can you use either the PGPASSWORD environment or the pgpassfile (for
> > 7.3)
> > functionality?
> >
> > http://bugzilla.bricolage.cc/show_bug.cgi?id=287
>
> Uh, no. The password goes into bricolage.conf. If you leave it blank,
> it'll default to "nalletsac" in Bric::Config. I could probably change
> that, though, to check for PGPASSWORD, first. Then you'd just have to
> add
>
> PerlPassEnv PGPASSWORD

I'd actually been thinking the other direction.

If I understood the bugzilla entry correctly, you want to shell to
a psql, can you set the environment for that particular exec to have the
password environment (from wherever you get it)?

-------------------------------------------------------
This SF.NET email is sponsored by: Thawte.com - A 128-bit supercerts will
allow you to extend the highest allowed 128 bit encryption to all your
clients even if they use browsers that are limited to 40 bit encryption.
Get a guide here:http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0030en
_______________________________________________
Bricolage-General mailing list
Bricolage-General@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bricolage-general

[Bricolage-General] Re: [Bricolage-Bugs] [Bug 287] Our SQL Parsing is Bogus [ In reply to ]

david at wheeler

Jan 17, 2003, 8:09 AM

Post #3 of 8 (1291 views)

Permalink

On Friday, January 17, 2003, at 08:00 AM, Stephan Szabo wrote:

> I'd actually been thinking the other direction.
>
> If I understood the bugzilla entry correctly, you want to shell to
> a psql, can you set the environment for that particular exec to have
> the
> password environment (from wherever you get it)?

Oh. My apologies for misunderstanding. It looks like, from the psql
documentation, that it doesn't support the use of the usual PG*
environment variables. :-(

David

--
David Wheeler AIM: dwTheory
david@wheeler.net ICQ: 15726394
http://david.wheeler.net/ Yahoo!: dew7e
Jabber: Theory@jabber.org

-------------------------------------------------------
This SF.NET email is sponsored by: Thawte.com - A 128-bit supercerts will
allow you to extend the highest allowed 128 bit encryption to all your
clients even if they use browsers that are limited to 40 bit encryption.
Get a guide here:http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0030en
_______________________________________________
Bricolage-General mailing list
Bricolage-General@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bricolage-general

[Bricolage-General] Re: [Bricolage-Bugs] [Bug 287] Our SQL Parsing is Bogus [ In reply to ]

sszabo at megazone23

Jan 17, 2003, 8:40 AM

Post #4 of 8 (1288 views)

Permalink

On Fri, 17 Jan 2003, David Wheeler wrote:

> On Friday, January 17, 2003, at 08:00 AM, Stephan Szabo wrote:
>
> > I'd actually been thinking the other direction.
> >
> > If I understood the bugzilla entry correctly, you want to shell to
> > a psql, can you set the environment for that particular exec to have
> > the
> > password environment (from wherever you get it)?
>
> Oh. My apologies for misunderstanding. It looks like, from the psql
> documentation, that it doesn't support the use of the usual PG*
> environment variables. :-(

It seems to actually work however when I try it in a shell:

export PGPASSWORD=foo1
psql

gets me in without a prompt, while I get prompted if I don't have the
environment variable set. I am using 7.4 devel, but I don't think that's
likely to have changed (apart from it being semi-deprecated in favor of
the .pgpass solution).

-------------------------------------------------------
This SF.NET email is sponsored by: Thawte.com - A 128-bit supercerts will
allow you to extend the highest allowed 128 bit encryption to all your
clients even if they use browsers that are limited to 40 bit encryption.
Get a guide here:http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0030en
_______________________________________________
Bricolage-General mailing list
Bricolage-General@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bricolage-general

[Bricolage-General] Re: [Bricolage-Bugs] [Bug 287] Our SQL Parsing is Bogus [ In reply to ]

david at wheeler

Jan 17, 2003, 8:50 AM

Post #5 of 8 (1286 views)

Permalink

On Friday, January 17, 2003, at 08:40 AM, Stephan Szabo wrote:

> It seems to actually work however when I try it in a shell:
>
> export PGPASSWORD=foo1
> psql
>
> gets me in without a prompt, while I get prompted if I don't have the
> environment variable set. I am using 7.4 devel, but I don't think
> that's
> likely to have changed (apart from it being semi-deprecated in favor of
> the .pgpass solution).

Well I'll be damned. Thanks for that, Stephan! I wish that was
documented in the psql man page!

Regards,

David

--
David Wheeler AIM: dwTheory
david@wheeler.net ICQ: 15726394
http://david.wheeler.net/ Yahoo!: dew7e
Jabber: Theory@jabber.org

-------------------------------------------------------
This SF.NET email is sponsored by: Thawte.com - A 128-bit supercerts will
allow you to extend the highest allowed 128 bit encryption to all your
clients even if they use browsers that are limited to 40 bit encryption.
Get a guide here:http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0030en
_______________________________________________
Bricolage-General mailing list
Bricolage-General@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bricolage-general

[Bricolage-General] Re: [Bricolage-Bugs] [Bug 287] Our SQL Parsing is Bogus [ In reply to ]

sszabo at megazone23

Jan 17, 2003, 10:01 AM

Post #6 of 8 (1287 views)

Permalink

On Fri, 17 Jan 2003, David Wheeler wrote:

> On Friday, January 17, 2003, at 08:40 AM, Stephan Szabo wrote:
>
> > It seems to actually work however when I try it in a shell:
> >
> > export PGPASSWORD=foo1
> > psql
> >
> > gets me in without a prompt, while I get prompted if I don't have the
> > environment variable set. I am using 7.4 devel, but I don't think
> > that's
> > likely to have changed (apart from it being semi-deprecated in favor of
> > the .pgpass solution).
>
> Well I'll be damned. Thanks for that, Stephan! I wish that was
> documented in the psql man page!

I think it's actually documented as part of libpq so I assume any
program that uses libpq gets the behavior if they don't explicitly pass
connection information.

-------------------------------------------------------
This SF.NET email is sponsored by: Thawte.com - A 128-bit supercerts will
allow you to extend the highest allowed 128 bit encryption to all your
clients even if they use browsers that are limited to 40 bit encryption.
Get a guide here:http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0030en
_______________________________________________
Bricolage-General mailing list
Bricolage-General@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bricolage-general

[Bricolage-General] Re: [Bricolage-Bugs] [Bug 287] Our SQL Parsing is Bogus [ In reply to ]

david at wheeler

Jan 17, 2003, 10:03 AM

Post #7 of 8 (1285 views)

Permalink

On Friday, January 17, 2003, at 10:01 AM, Stephan Szabo wrote:

> I think it's actually documented as part of libpq so I assume any
> program that uses libpq gets the behavior if they don't explicitly pass
> connection information.

Yeah, makes sense. However, most people who use psql in general
probably aren't going to go reading up on the client C library
documentation. I know I wouldn't.

DBD::Pg at least documents this functionality itself.

Regards,

David

--
David Wheeler AIM: dwTheory
david@kineticode.com ICQ: 15726394
Yahoo!: dew7e
Jabber: Theory@jabber.org
Kineticode. Setting knowledge in motion.[sm]

-------------------------------------------------------
This SF.NET email is sponsored by: Thawte.com - A 128-bit supercerts will
allow you to extend the highest allowed 128 bit encryption to all your
clients even if they use browsers that are limited to 40 bit encryption.
Get a guide here:http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0030en
_______________________________________________
Bricolage-General mailing list
Bricolage-General@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bricolage-general

[Bricolage-General] Re: [Bricolage-Bugs] [Bug 287] Our SQL Parsing is Bogus [ In reply to ]

sszabo at megazone23

Jan 17, 2003, 10:06 AM

Post #8 of 8 (1287 views)

Permalink

On Fri, 17 Jan 2003, David Wheeler wrote:

> On Friday, January 17, 2003, at 10:01 AM, Stephan Szabo wrote:
>
> > I think it's actually documented as part of libpq so I assume any
> > program that uses libpq gets the behavior if they don't explicitly pass
> > connection information.
>
> Yeah, makes sense. However, most people who use psql in general
> probably aren't going to go reading up on the client C library
> documentation. I know I wouldn't.

I agree it's non-sensical to expect people to read that documentation
for it. I think there was talk of pulling that out into its own
entry and cross referencing it as necessary, but I don't follow
documentation threads closely.

-------------------------------------------------------
This SF.NET email is sponsored by: Thawte.com - A 128-bit supercerts will
allow you to extend the highest allowed 128 bit encryption to all your
clients even if they use browsers that are limited to 40 bit encryption.
Get a guide here:http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0030en
_______________________________________________
Bricolage-General mailing list
Bricolage-General@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bricolage-general