When you want to punch yourself in the head
-
I'm running a process that I wrote years ago, and evidently when I hit a point where data corruption occurred I felt the need to rub my future self's nose in it rather than fix the issue. This message just popped up at the end of the failed run:
Quote:
IDs have changed. If you rely on IDs, you're screwed
Thanks past me. :mad:
cheers Chris Maunder
-
I'm running a process that I wrote years ago, and evidently when I hit a point where data corruption occurred I felt the need to rub my future self's nose in it rather than fix the issue. This message just popped up at the end of the failed run:
Quote:
IDs have changed. If you rely on IDs, you're screwed
Thanks past me. :mad:
cheers Chris Maunder
-
I'm running a process that I wrote years ago, and evidently when I hit a point where data corruption occurred I felt the need to rub my future self's nose in it rather than fix the issue. This message just popped up at the end of the failed run:
Quote:
IDs have changed. If you rely on IDs, you're screwed
Thanks past me. :mad:
cheers Chris Maunder
I rub my future self's nose in it every chance I get, because he is smug and arrogant, which really irritates me. Besides, there's no chance he can retaliate, so I figure "Why Not?"
-
I'm running a process that I wrote years ago, and evidently when I hit a point where data corruption occurred I felt the need to rub my future self's nose in it rather than fix the issue. This message just popped up at the end of the failed run:
Quote:
IDs have changed. If you rely on IDs, you're screwed
Thanks past me. :mad:
cheers Chris Maunder
Chris Maunder wrote:
Thanks past me.
Now, what would have been cool, is if your past me recommended a solution, using today's technology and best practices.
-
I'm running a process that I wrote years ago, and evidently when I hit a point where data corruption occurred I felt the need to rub my future self's nose in it rather than fix the issue. This message just popped up at the end of the failed run:
Quote:
IDs have changed. If you rely on IDs, you're screwed
Thanks past me. :mad:
cheers Chris Maunder
Chris Maunder wrote:
IDs have changed.
:wtf: If it changes it's not an ID.
Wrong is evil and must be defeated. - Jeff Ello
-
Chris Maunder wrote:
IDs have changed.
:wtf: If it changes it's not an ID.
Wrong is evil and must be defeated. - Jeff Ello
Yes. You'd think so, right? You tell that to the data providers we use. After you get them to keep IDs consistent you can work on getting them to normalise their data or even better: be consistent with quotes around integers in CSV files (hint: you don't put quotes around integers in CSV files. You most especially don't put quotes around the values on random rows)
cheers Chris Maunder
-
Yes. You'd think so, right? You tell that to the data providers we use. After you get them to keep IDs consistent you can work on getting them to normalise their data or even better: be consistent with quotes around integers in CSV files (hint: you don't put quotes around integers in CSV files. You most especially don't put quotes around the values on random rows)
cheers Chris Maunder
There are no emoticons that sufficiently describes what I feel about that. This is one of the reasons I don't trust NoSQL. A former co-worker of mine is now working for a major car manufacturer (no, not the local one), the database he's working against isn't normalized. "It's not necessary, It's handled in code". Well, apparently it wasn't.
Wrong is evil and must be defeated. - Jeff Ello
-
I'm running a process that I wrote years ago, and evidently when I hit a point where data corruption occurred I felt the need to rub my future self's nose in it rather than fix the issue. This message just popped up at the end of the failed run:
Quote:
IDs have changed. If you rely on IDs, you're screwed
Thanks past me. :mad:
cheers Chris Maunder
-
Yes. You'd think so, right? You tell that to the data providers we use. After you get them to keep IDs consistent you can work on getting them to normalise their data or even better: be consistent with quotes around integers in CSV files (hint: you don't put quotes around integers in CSV files. You most especially don't put quotes around the values on random rows)
cheers Chris Maunder