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: "WORENKLEIN, David, GCM" <David dot Worenklein at gcm dot com>
Subject: RE: bcp and select, not the same time?
Date: Jul 30 1999 4:03PM

Probably not.  You are deadlocked, but Sybase doesn't know that process A is
waiting for process B, and vice versa.

Sybase will only kill deadlocks if it knows they're deadlocked.  It thinks
process B is blocked by process A, and process A is just being rude and
taking its time.

-----Original Message-----
From: AGHZHONG@aol.com [mailto:AGHZHONG@aol.com]
Sent: Friday, July 30, 1999 10:07 AM
To: SybPerl Discussion List
Subject: Re: bcp and select, not the same time?


I have another idea.

Since I need to select from and bcp in to the same table and it dead locks 
when
I have both in one program,  it might work if I use a named pipe, one
program
selects and assembles the data and write to named pipe,  the other bcp in 
program
read from the pipe.  I know this would not prevent deadlock in Sybase,  but
at least there are two processes (versus one as before) trying to fight for 
the locks
and Sybase should know to kill one process and go on.  

Will this work?
Thanks
Heather