PEPPLER.ORG
Michael Peppler
Sybase Consulting
Menu
Home
Sybase on Linux
Install Guide for Sybase on Linux
General Sybase Resources
General Perl Resources
Freeware
Sybperl
Sybase::Simple
DBD::Sybase
BCP Tool
Bug Tracker
Mailing List Archive
Downloads Directory
FAQs
Sybase on Linux FAQ
Sybperl FAQ
Personal
Michael Peppler's resume

sybperl-l Archive

Up    Prev    Next    

From: "Edward J dot Sabol" <sabol at alderaan dot gsfc dot nasa dot gov>
Subject: Re: BLK API for DBD::Sybase...
Date: Jul 9 2004 7:15PM

> The way I see it I have two choices:
> 1. Store the rowcount somewhere (e.g. $sth->{syb_bcp_rows_affected})
> or
> 2. Don't use commit/rollback/finish, and instead create an ad-hoc
> private method ($sth->syb_bcp_commit(\$rows), etc).

I think I would vote for (1), but could you post code snippets of each being
used? I'm not sure I follow exactly, and concrete code to look at would help
a lot. I suspect that the commit/rollback/finish methods would be the least
surprising. How would $sth->{syb_bcp_rows_affected} relate to $sth->rows?

Thanks,
Ed