freetds AT lists.ibiblio.org
Subject: FreeTDS Development Group
List archive
- From: "Thompson, Bill D (London)" <bill_d_thompson AT ml.com>
- To: "'FreeTDS Development Group'" <freetds AT lists.ibiblio.org>
- Subject: RE: [freetds] News about this bug?
- Date: Fri, 23 Jan 2004 11:26:09 -0000
Thanks Freddy,
I'll put this on my TODO.
I've lost any memory I had of this issue/bug .
Do we have a test case / program or a more detailed description of the issue
?
merge publication seems to be something to do with replication ?
Bill
> -----Original Message-----
> From: ZIGLIO, Frediano, VF-IT [SMTP:Frediano.Ziglio AT vodafone.com]
> Sent: 23 January 2004 11:00
> To: FreeTDS Development Group
> Subject: RE: [freetds] News about this bug?
>
> > >
> > > Update/delete returns -1 instead of correct affected rows on Merge
> > > Publication on MSSQL 2000 SP3a.
> > >
> > > Any news?
> > > Thanks.
> > >
> >
> > If you refer to ctlib problem with triggers nothing changed.
> > We still do
> > not know if this is a bug...
> >
> > ciao,
> > freddy77
>
> Well, from ct_res_info help:
>
> Retrieving the command number for the current result set
>
> * To determine the number of the command that generated the current
> result set, call ct_res_info with result_typeas CS_CMD_NUMBER.
>
> * Client-Library keeps track of the command number by counting the
> number of times ct_results returns CS_CMD_DONE.
>
> ....
>
> Inside stored procedure or transactions, only select statements cause
> the command number to be incremented. If a stored procedure or
> transaction contains seven SQL commands, three of which are select
> statements, the command number that ct_res_info returns can be any
> integer from 1 to 3, depending on which select statement generated the
> current result set.
>
> ...
>
> If the command is one that executes a stored procedure or transaction,
> for example a Transact-SQL exec language command or a remote procedure
> call, ct_res_info returns either the number of rows returned by the
> latest select statement executed by the stored procedure or transaction,
> or CS_NO_COUNT if the stored procedure or transaction does not execute
> any select statements. A stored procedure or transaction that does not
> contain a select statement can execute a select by calling another
> stored procedure or transaction that contains a select.
>
>
> So it seem that even CTLib should ignore TDS_DONEIN_PROC is no columns
> are present...
>
> freddy77
> _______________________________________________
> FreeTDS mailing list
> FreeTDS AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/freetds
-
[freetds] News about this bug?,
Stefano Coletta, 01/23/2004
- <Possible follow-up(s)>
- RE: [freetds] News about this bug?, ZIGLIO, Frediano, VF-IT, 01/23/2004
- RE: [freetds] News about this bug?, ZIGLIO, Frediano, VF-IT, 01/23/2004
-
RE: [freetds] News about this bug?,
Thompson, Bill D (London), 01/23/2004
- Re: [freetds] News about this bug?, Stefano Coletta, 01/23/2004
- RE: [freetds] News about this bug?, ZIGLIO, Frediano, VF-IT, 01/23/2004
Archive powered by MHonArc 2.6.24.