[TYPO3-dev] dbal with SQL Server 2000, value type mismatch when saving records in backend

[Robert Böttner]

Hi Masi,

thanks for the reply.

> Does the update really fail or is it "just" an error message in the BE? 
Inserts and updates actually fail, no data gets written for the binary 
fields. All data of non-binary fields are properly written. This is 
because binary fields are first excluded from the insert/update and 
filled with NULL values in dbal. They are then looped each one 
exclusively for an individual check of each of them and then written 
with the actual value.

I have this general ODBC driver setting in my odbcinst.ini:

[ODBC]
Trace		= Yes
TraceFile	= /tmp/sql.log
ForceTrace	= Yes
Pooling		= No

FreeTDS also returns the field type mismatch in the executed sql 
statements in /tmp/sql.log

Good night
Robert.