Menu ▾ ▴

#4062 Setting BLOB to null gives incorrect number of affected rows

Latest_Git
works-for-me
nobody
None
5
2013-09-10
2013-08-16
Isaac Bennetch
No

If you update a row with a BLOB column and set it to NULL, the operation works but says 0 rows affected, which obviously is an incorrect row count.

This is another one of my notes from DebConf

Discussion

  • Isaac Bennetch

    Isaac Bennetch - 2013-08-16
    • summary: Setting BLOB tonull gives incorrect number of affected rows --> Setting BLOB to null gives incorrect number of affected rows
     

  • Abhishek Kandoi

    Abhishek Kandoi - 2013-08-19

    I am unable to reproduce this bug.

    I tried updating a row and set its Blob column content to NULL. As a result it showed me that one row was affected.

    Can you provide some details on how do I reproduce this bug?

     

  • Marc Delisle

    Marc Delisle - 2013-09-04
    • status: open --> pending
     

  • Marc Delisle

    Marc Delisle - 2013-09-10
    • status: pending --> works-for-me