> I tried replacing "DSN" with "Postgresql" and "PostgreSQL" and I got the
> same error. I don't remember doing anything with any control panel, and I
> don't know where to find the proper DSN. I see now that if I searched the
> DBI module documentation for "environment" rather then "environmental" I
> would have learned which environmental variable to set, but I still wouldn't
> know what to set it with.
Ok, I would guess that the Perl module looks for an existing odbc connection that existed on that same client. Did you install the postgresql odbc driver on the pc you are trying to connect from? That is where the DSN name would come from. For ODBC a connection must be created on each client. It can be manually done through the control panel. You could try connecting to the db through another program like MS Access which would use an ODBC connection. Then you would know it is a problem with the Perl ODBC module for sure. I don't know if the driver is included in the perl odbc module for windows. I installed the postgres odbc driver from gborg well before using the Perl modules.
Things have changed a bit from 7.3.4 which is the link mentioned below. The default install from cygwin has been 7.4.1 for a while. 7.4.2 was just released in cygwin. I haven't tried to upgrade from .1 yet.....
Mysql has it's own plusses and minuses. Can't answer which one would be better for your situation. Sorry.
In a few months a native windows version of Postgresql will be available so if you really want to avoid cygwin and can wait a bit that would be an option.
> If I remember correctly, I just followed the first two instructions at
> http://www.postgresql.org/docs/faqs/text/FAQ_MSWIN then I decided not to do
> the basic installation because I don't want to be limited, so I followed the
> "NT services Cygwin PostgreSQL installation procedure" at
> http://www.tishler.net/jason/software/postgresql/postgresql-7.3.4.README . I
> had to search for the solutions to many problems that I encountered along
> the way--in other words, the instructions didn't work. I found most
> solutions, including the proper way to set environmental variables, other
> packages that needed installing, and chmod commands that "usually" solve one
> of the problems (the last email to this list, from David, lists those
> commands, which are included in the instructions I was following, but in a
> bad place), but now I have this problem with the DSN. This is why I didn't
> read the entire documentation for DBD::ODBC and DBI. I had no confidence
> that it would have helped me and I needed step-by-step confirmation that
> stuff is working, starting with an initial connection to the database.
> I'm seriously considering avoiding anything that requires Cygwin. I'll
> either use MySQL or I could build a suitable storage solution for my needs
> in less than one day. Trying to get PostgreSQL to work has taken me a week,
> and I'd still have to learn SQL after that.
> Sorry if this post isn't in the spirit of this list. I appreciate the help,
> but I just about had enough.
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
In response to
pgsql-cygwin by date
|Next:||From: Leeuw van der, Tim||Date: 2004-06-14 10:15:43|
|Subject: Re: Updated Cygwin Package: postgresql-7.4.2-1|
|Previous:||From: David P. Lurie||Date: 2004-06-13 23:42:30|
|Subject: WARNING: dup(0) failed after 3195 successes: Bad file descriptor|