Darnit. That was what I was going to say.
I just committed this sin today.
I added it as temporary code while I fix the real issue. I have a listbox-style control that doesn't like overlapping datetimes in the control, but some of our systems have bad date time data as they are development systems and didn't have the code in place to keep them from putting in the bad data in the first place.
I chucked this in and am doublechecking that new systems can't get bad data and then to also write a method to ignore duplicate datetime event data.
If it gets through, the data is so unimportant that it should never matter. (and now I just jinxed that, so better get back to work to fix the real issue)
Darnit. That was what I was going to say.
I just committed this sin today.
I added it as temporary code while I fix the real issue. I have a listbox-style control that doesn't like overlapping datetimes in the control, but some of our systems have bad date time data as they are development systems and didn't have the code in place to keep them from putting in the bad data in the first place.
I chucked this in and am doublechecking that new systems can't get bad data and then to also write a method to ignore duplicate datetime event data.
If it gets through, the data is so unimportant that it should never matter. (and now I just jinxed that, so better get back to work to fix the real issue)