Looks like you're out of luck:
http://www.thetechtwo.com/detail-11479407.html

You basically have to buy a JDBC or ODBC client for it (how lovely!) and then hope that the various JDBC connectors or DBD::ODBC properly work with it.

H

On May 4, 2006, at 1:16 PM, H.Merijn Brand wrote:

On Thu, 4 May 2006 11:58:34 +0200, [EMAIL PROTECTED] wrote:

Mr. Brand -

I'll reply off-list, since you say dbi-dev is the incorrect one (which
would you recommend)?

dbi-users

I'd like to know why you suggest DBD::Pg for Progress.  DBD::Pg is
advertised as being for Postgres, which is an open-source database.

The Progress RDBMS is decidedly NOT open-source (see www.progress.com).
Indeed, one of the problems my management has with it are what they
consider exhorbitant license fees.

I stand corrected. I blame the more ignorant users that typo this database
soooo often that I read everything posted like this as a request for
PostgreSQL.

So, my question is: does the Postgres stuff work for Progress? Or will I have to write a new DBD module to obtain a direct connection (which is why
I asked on dbi-dev)?

In that case, you might have been right in the first place for choosing this list. I've put it back here, as your questions are very valid. Sorry again.

Now for the real question.

I also do not see a Postgress DBD on CPAN, which doesn't mean it doesn't exist, it only proves that if someone has done it, he or she never put it on
CPAN.

I do not know how Progress interfaces. If it uses E/SQL find a driver that
uses a lot of that (DBD-Unify, FreeTDS, and Ingres might be helpful in
scanning). If you are HLI (c library calls), then use DBD-Oracle and DBD-ODBC
as guidance

Read DBD.pm, as in
# man DBI::DBD
or
# perldoc DBI::DBD

--
H.Merijn Brand Amsterdam Perl Mongers (http:// amsterdam.pm.org/) using & porting perl 5.6.2, 5.8.x, 5.9.x on HP-UX 10.20, 11.00, 11.11, & 11.23, SuSE 10.0, AIX 4.3 & 5.2, and Cygwin. http:// qa.perl.org http://mirrors.develooper.com/hpux/ http://www.test- smoke.org http://www.goldmark.org/jeff/stupid- disclaimers/

Reply via email to