Skip to Content.
Sympa Menu

freetds - RE: [freetds] Status: bcp

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Castellano, Nicholas" <Nicholas_Castellano AT acml.com>
  • To: 'FreeTDS Development Group' <freetds AT lists.ibiblio.org>
  • Subject: RE: [freetds] Status: bcp
  • Date: Fri, 19 Dec 2003 12:23:38 -0500


> From: Lowden, James K
> Sent: Friday, December 19, 2003 12:09 PM
> To: 'FreeTDS Development Group'
> Subject: RE: [freetds] Status: bcp
>
> Thanks, Nick, I see I have to modify my theory to fit the
> facts. Bill linked my new bcp.c unit test to Sybase's
> libraries, and got no message. His experience matches mine:
> I've never seen that or coded against it.
>
> It would make sense that bcp_batch() would not emit that
> message, because the application *knows* the batch was just
> committed based on the return code from bcp_batch().
>
> It would also make sense for bcp_exec() to emit that message
> if BCP_SETL had been called to set a batch size for the
> loading of an external file. There's no other way the
> application could be notified of the ongoing status of the load.

OK, then perhaps just moving the code to emit that message, or
conditionalizing it, might fix your problem while leaving the bcp_exec()
behavior intact. I can probably look into it early next week if you don't
get to it sooner.

-----------------------------------------
The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above. If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the original
message. Please note that we do not accept account orders and/or instructions
by e-mail, and therefore will not be responsible for carrying out such orders
and/or instructions.






Archive powered by MHonArc 2.6.24.

Top of Page