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

[Karsten Dambekalns]

Hi.

Robert Böttner wrote:
> 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.

Right, this was the only way to do it cross-db. Why excatly does it fail 
for you? Is NULL disallowed? Does the later update fail?

Regards,
Karsten