Using Sybperl has the advantage that your API is quite close to the Sybase C libraries. If you are working in an environment where they use other languages to connect to Sybase, it does have its advantages to use a common API. I've worked in an environment where our products were written in C, using Sybase DB library (yeah, this was a while ago). I used Sybperl to help developers write their code by prototyping, debugging and optimizing.
I can't claim Sybperl is easier than the DBI - or that it's harder. If all you are doing is connecting to the database and repeat the cycle: prepare/execute/fetch/fetch/fetch, they're both simple. But the Sybase API is much richer than the API of the DBI (which is obvious, the API of the DBI needs to work for all databases). So you can probably write slightly more efficient code using Sybperl (but you probably needs very good knowledge of both Sybase and your data to be able to do so).
Another reason I liked Sybperl was the fact that I used to have the complete Sybase manuals available in dead tree format (but their manuals are available on-line as well: sybooks.sybase.com. One of the few software products which has a (free) manual more extensive and better than Perl)
In reply to Re: Sybperl vs Perl 5.8.4 DBI
by Anonymous Monk
in thread Sybperl vs Perl 5.8.4 DBI
by azstyx
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |