Re: When the column typing error is matched, compulsion ROLLBACK is generated.

Hi James

Thanks for your reply.

> Could you please post a patch demonstrating your "correction"?  I don't
know what you mean by "ROLLBACK was compulsorily issued by FreeTDS".  Are
you referring to autocommit?

A "column type mismatch" error example below.
"colbit" is bit type.
It tries to set "A" to it.

*SQL:  UPDATE [testtable] SET [colbit] = 'A' WHERE testtableid = '1';
*ErrorMessage: SQLSTATE[HY000]: General error: 20018 The ROLLBACK
TRANSACTION request has no corresponding BEGIN TRANSACTION. [20018]
(severity 5) []

A similar case was reported on the following sites.

http://efreedom.com/Question/1-2296573/Rollback-Error-Saving-Incorrect-Data-Column



2011/1/23 James K. Lowden <[email protected]>

> On Fri, 21 Jan 2011 17:21:17 +0900
> ???? <[email protected]> wrote:
>
> > I use FreeTDS for the connection from PHP on Linux to MSSQL.
> > When SQL transaction that became an error of the column type mismatch was
> > executed, ROLLBACK was compulsorily issued by FreeTDS.
> > (Compulsion ROLLBACK is not generated at other SQL errors.)
> > I completed the correction of the source, and had SQL of the column type
> > mismatch not requested now.
>
> Could you please post a patch demonstrating your "correction"?  I don't
> know what you mean by "ROLLBACK was compulsorily issued by FreeTDS".  Are
> you referring to autocommit?
>
> AFAIK, the FreeTDS ODBC driver never spontaneously issues a ROLLBACK
> request to the server.  Transactions are under application control via
> SQLTransact().
>
> > Is it a specification of FreeTDS that ROLLBACK is compulsorily issued
> when
> > the error of SQL of the column type mismatch is issued?
>
> I do not understand what you mean by "column type mismatch".
>
> --jkl
> _______________________________________________
> FreeTDS mailing list
> [email protected]
> http://lists.ibiblio.org/mailman/listinfo/freetds
>