![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I remember when I worked in Ingres we used "Ingperl" and when the Perl DBD for Ingres came out we migrated all our perl scripts away from Ingperl. I'm contemplating introducing Perl on our servers (management fear of anything bar shell scripts being ignored) and I'm wondering if anyone can weigh up the pros and cons for Sybperl and DBD::Sybase. Are people gradually moving onto DBD? Is Sybperl dominant? What are the functionality benefits from each? Any views welcome. |
#3
| |||
| |||
|
|
I'm wondering if anyone can weigh up the pros and cons for Sybperl and DBD::Sybase. Are people gradually moving onto DBD? |
#4
| |||
| |||
|
|
"Martin Hanna" <postmaster (AT) SPAMIGNOREmovillaIGNOREplus (DOT) com> writes: I find the DBI interface much more convenient, particularly for error handling. A bonus is that you can use the same style of code for Sybase and other RDBMSes. |
#5
| |||
| |||
|
|
"Ed Avis" <ed (AT) membled (DOT) com> wrote in message news:l1lljy12xk.fsf (AT) budvar (DOT) future-i.net... "Martin Hanna" <postmaster (AT) SPAMIGNOREmovillaIGNOREplus (DOT) com> writes: I find the DBI interface much more convenient, particularly for error handling. A bonus is that you can use the same style of code for Sybase and other RDBMSes. That's my key interest. If I can code a connection to the DBI, whether the DBD is Sybase, Sql Server, Oracle or whatever, the code change is minimal or none. |
![]() |
| Thread Tools | |
| Display Modes | |
| |