On 4/18/2011 5:31 PM, Ken Kixmoeller (ProFox) wrote: > OK, anyone out there have a WAG about this? > > In a system I have that uses MySQL as the data store, I need to update > 2 fields to fix a data error that resulted from a bug that some idiot > programmer introduced. (This particular idiot shall go unnamed, but he > is the sole author of this particular application.) > > Here is the situation: > > -- two fields were left blank > -- there are 2 *other* fields which are redundant 99% of the time (and > in 100% of these cases). > -- I ran a simple query: > > Update the_table set field_A = field_B, field_C = field_D where > field_a = 0 > > -- The intended result was fine, but there was an unintended > additional result: field_F was set to 14 in all of the affected > records. > > There are no stored procedures in the database at all, much less > pertaining to this table and field. > > I'm stumped.
Are you able to replicate this weird behavior consistently? Are you sure no other hands are in the soup (app) adjusting data? -- Mike Babcock, MCP MB Software Solutions, LLC President, Chief Software Architect http://mbsoftwaresolutions.com http://fabmate.com http://twitter.com/mbabcock16 _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
