Sybperl x DBI x DBD::Sybase
André Castanheira
I'm a bit confusing.
What's the difference between Sybperl , DBI and DBD::Sybase ?
I know that DBI is a Perl API to connect to wichever database you
choose.
I use sybase, so I use sybperl to connect to ASE and create some cgi
scripts. But I would like to know if DBI is better or if it also needs
sybperl.
If somebody could explain to me ?
Thanks,
André
Bernd Dulfer
> I'm a bit confusing.
> What's the difference between Sybperl , DBI and DBD::Sybase ?
> I know that DBI is a Perl API to connect to wichever database you
> choose.
well, basically they do the same. to connect perl to a sybase database
you can use either sybperl or dbi/dbd::sybase.
afaik dbd::sybase uses the new ct-library
adn the construction dbi/dbd is more flexible if you want to connect to
different dbms
>
> I use sybase, so I use sybperl to connect to ASE and create some cgi
> scripts. But I would like to know if DBI is better or if it also needs
> sybperl.
dbi needs dbd, but not sybperl.
i'd say dbi/dbd is the new way
rgds
--
Bernd Dulfer
Sybase Professional Services Germany
bdu...@sybase.com
Sybase Manuals: http://sybooks.sybase.com
Sybase FAQ: http://www.isug.com/Sybase_FAQ
Sent via Deja.com http://www.deja.com/
Before you buy.
Michael Peppler
"=?iso-8859-1?Q?Andr=E9?= Castanheira"
<andre.ca...@cariocaengenharia.com.br> wrote:
> I use sybase, so I use sybperl to connect to ASE and create some cgi
> scripts. But I would like to know if DBI is better or if it also needs
> sybperl.
sybperl (composed of the Sybase::DBlib and Sybase::CTlib modules)
implements access to the native Sybase OpenClient APIs. The code is
mature (I first started working on sybperl over 10 years ago!) and gives
you direct access to most of the Sybase API, and hence a lot of
flexibility, and better control for things like error handling, TEXT
column handling, RPC calls, etc.
DBD::Sybase is much younger, although it's also quite solid now. As you
know if implements the DBI API, which gives you access to most normal
features, but does not allow you to control some of the more esoteric
features of the Sybase API.
For simple jobs you can choose either of these APIs - it won't make much
difference.
For more complex jobs I personally prefer sybperl (Sybase::CTlib,
specifically) because I like the control it gives me, and because I have
not (yet) had to write code that would have to run against non-Sybase
databases.
If you want your perl scripts to be (potentially) portable to non-Sybase
environments then you should use DBI/DBD::Sybase.
Michael
--
Michael Peppler - Data Migrations Inc. - mpep...@peppler.org
http://www.mbay.net/~mpeppler - mpep...@mbay.net - AIM MPpplr
International Sybase User Group - http://www.isug.com
Sybase on Linux mailing list: ase-lin...@isug.com