I'm trying make DBD::Oracle on Macintosh OS X.
DBI-1.30 compiled and tested cleanly.
I'm attaching the entire output of:
perl Makefile.PL for DBD::Oracle 1.12
Other than minor errors like:
Multiple copies of Driver.xst found in: /Library/Perl/darwin/auto/DBI
/Library/Perl/darwin/auto/DBI at
Thannk you very much for your patience. But after hours I finally found
the answer myself. It's as stunningly silly as always: Never put an
open db handler on a cache - and never try to revive it later... -:D
Michael A Chase wrote:
On Thu, 29 Aug 2002 15:31:03 +0200 THC Soft [EMAIL PROTECTED]
Hi,
Sorry to bother you!
I use your DBI moudle to install in hp server. But, it faill to compile.
Because it use gcc to make compile.
Do you have any version of DBI moudle to use ansi c to compile?
Thanks!
Here is the error message for your reference.
% make
/bin/perl
1. I am doing everything in my notebook with win2000 and I log on as
administrator. Apache is started by apache -f myhttpd.conf -k start.
Does this mean that the user running apache service is administrator? I
have checked the DBD::ODBC doc and got no more clues except for defining a
Did you look at the new ParamValues attribute? Yes, many drivers probably
do not support it yet, but that's what it's for. (Also, DBD::ODBC does
support it and I believe that even if DBD::Oracle doesn't yet support it a
small lift of the same/similar code from DBD::ODBC to DBD::Oracle should
Jeff Urlwin [EMAIL PROTECTED] wrote:
2. The perl I use is also Activeperl build 633. I have no idea why I
cannot install dbd::odbc succesfully.
I don't know. It might be a flag in the ppd file, but the ppd is
generated by MakeMaker directly. It also says, in the ppd file, that
the
Set up DBD::JDBC to use a (god help me) a Microsoft supplied JDBC driver
for MS SQL Server 2000. Can't seem to get past the error:
install_driver(JDBC) failed: Bareword SQL_BIGINT not allowed while
strict subs in use at /usr/local/lib/perl5/site_perl/5.6.1/DBD/JDBC.pm
line 1028.
BEGIN not safe
Recent versions of DBI removed SQL_BIGINT from it's definition as there was
a conflict between SQL/CLI and ODBC's definition. I suspect you need to
hack up JDBC.pm to not use it...
Regards,
Jeff (who ran into this issue with DBD::ODBC)
P.S. I take it you want DBD::JDBC due to the thin
