Go to the
DBI Mailing Lists Archive
and see for yourself ...
Christian Lemburg
Brainbench MVP for Perl
http://www.brainbench.com
| [reply] |
I suspect that this bug is what is being referred to?
In which case there is a bug, but it isn't that bad.
FWIW about a year ago using DBD::Sybase was pretty painful, there were several bugs that caught me. (Improper type conversions on nulls, etc.) But they got cleaned up around March or so IIRC and I have not been having problems since.
| [reply] |
I use both DBD::Sybase and Sybase::DBLib and CTLib at
my location. Michael Peppler wrote both, and as of the
last time I logged on to his web site, he seemed to think
that Sybase::DBLib, etcetera were the more full-featured.
I have
been a happy user of Sybperl since before it evolved into
Sybase::DBLib, CTLib, and BCP. We really don't use any
Sybperl features that DBD::Sybase lacks. The only thing
preventing me from rewriting old scripts is inertia. Our
new scripts are written using DBI/DBD.
DBD::Sybase is still evolving, but for most purposes it
suffices, and there is a lot to be said for doing new
scripts using DBI/DBD. If you ever are faced with the need
to migrate from one RDBMS to another, you will be quite
thankful that DBI/DBD exists.
One caveat, though -- Sybase ASE 12.0 has taken on a
new directory structure, and the client libraries are no
longer found at the root of $SYBASE. This can be worked
around by using $SYBASE as Sybase home, and placing a
symbolic link from usr/local/sybase to the new location of
the client libraries.
-----
"Computeri non cogitant, ergo non sunt" | [reply] |