From: | wes <pdxpug(at)the-wes(dot)com> |
---|---|
To: | Rich Shepard <rshepard(at)appl-ecosys(dot)com> |
Cc: | pdxpug(at)postgresql(dot)org |
Subject: | Re: Specifying Host With psycopg2 |
Date: | 2011-10-21 15:10:55 |
Message-ID: | CAA1wLO=Dkh9bVucOhtRoehHQFuP_tVCvLm+tQ4U8rd+q8bOmsg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pdxpug |
Interesting that your email has a date of 7 days ago, but only showed up
now. Maybe you got moderated?
Since this can be different from user to user, you should take the easy way
out and make the hostname configurable by the end-user. Something like a
configuration file with hostname, username, password, and perhaps database
name.
If you hard-code any of these things, you are asking for trouble.
-wes
On Fri, Oct 14, 2011 at 8:43 AM, Rich Shepard <rshepard(at)appl-ecosys(dot)com>wrote:
> I'm nut sure whether this is the appropriate list for my question; perhaps
> it belongs on the local python mail list. So, I'll ask:
>
> To identify the postgres host when establishing a connection to the
> database, should I use 'localhost,' the server's host name, or a
> fully-qualified path/host name?
>
> I'm asking because now I'll be developing and using this application here
> but eventually my client and a state regulatory agency will be using it on
> their Windows-based networks. My learning now just how to define the
> database host will make it easier for me when it comes time to provide the
> core python model to others.
>
> Rich
>
>
> --
> Sent via pdxpug mailing list (pdxpug(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/**mailpref/pdxpug<http://www.postgresql.org/mailpref/pdxpug>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Ewan, Michael | 2011-10-21 18:12:40 | Re: Specifying Host With psycopg2 |
Previous Message | Aaron Burt | 2011-10-20 19:56:58 | Re: CASE eval issue |