Up Prev Next
From: "Heinz Ringlhofer" <Heinz dot Ringlhofer at zamg dot ac dot at>
Subject: Re: Sybase-Simple vs DBD::Sybase
Date: Sep 13 2001 5:06PM
I assumed, this :-)
Thanks a lot ...
but to go a litle bit into detail ...
If the user fetches arrays of rows in a single call this gets memory bound.
Thats a problem on very large tables and very (you know what i mean)
On Sep 13, 15:36, Michael Peppler wrote:
> Subject: Re: Sybase-Simple vs DBD::Sybase
> Heinz Ringlhofer writes:
> > Now we want to move these techniques also out to our end-users.
> > Most of them are using a mixture of csh/isql scripts for automated
> > routine tasks right now.
> > As perl seems a much better choice, and pure Sybperl programming
> > might be too nuch to ask, we have 2 choices, either Sybase_Simple
> > or DBD.
> > I know DBD is more DB independent, but thats not one of our main
> > the main priority is getting better and more standardized "production"
> It's a somewhat difficult choice, as both will provide the necessary
> Using Sybase::Simple has the advantage of letting you use the
> Sybase::CTlib API on the same handle if you want/need to.
> DBD::Sybase uses the standardized DBI API, which may be easier for
> people to understand (and there is a book available).
> Personally I'd use Sybase::Simple, because it has APIs to fetch
> certain types of data structures with single calls, and so it is even
> easier to use than DBI - the user only has to know whether they need
> to fetch single rows, or single values, or lists of rows, etc.
> Only my opinion, of course :-)
> Michael Peppler - Data Migrations Inc. - http://www.mbay.net/~mpeppler
> firstname.lastname@example.org - email@example.com
> International Sybase User Group - http://www.isug.com
>-- End of excerpt from Michael Peppler