Lars Nilsson
Apr 16, 2016 1:56:55 AM

4294967295 Row(s) affected

I have just upgraded to the new version of WinSQL (64 bit) lite.

I always got a heart attack when I did a simple update in a database, and the program came back with the message in the heading. In earlier versions you got a message how many records where actually update, as per your selection criteria.

Is there a reason for this happening, and is there a way to get it back to the way it was in previous version?



Synametrics support engineer
Apr 19, 2016 11:11:46 AM

4294967295 Row(s) affected

Lars,

This is definitely a bug in WinSQL and it occurs when the ODBC driver is not able to return the number of rows affected. In that case, a -1 is returned. WinSQL tries to cast this -1 to an unsigned integer, resulting in Integer.MAX_VALUE.

We will fix this in the next build. However, you still won't see the actual number of rows affected since the back-end does not return this value. Instead, you will see something like "This command did not return data, and it did not return any rows"

Imran

Navigation

Social Media

Powered by 10MinutesWeb.com