Date: Mon, 10 Sep 2001 13:11:32 -0700 (PDT) From: John Polstra <jdp@polstra.com> To: hubs@freebsd.org Cc: roam@ringlet.net Subject: Re: CVSup upgrade to fix the timestamp bug Message-ID: <200109102011.f8AKBWJ51615@vashon.polstra.com> In-Reply-To: <20010910112417.C2053@ringworld.oblivion.bg> References: <20010909123920.G45219-100000@oahu.WURLDLINK.NET> <200109092255.f89Mtws48647@vashon.polstra.com> <20010909175836.M30764@curie.physics.purdue.edu> <20010910112417.C2053@ringworld.oblivion.bg>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <20010910112417.C2053@ringworld.oblivion.bg>, Peter Pentchev <roam@ringlet.net> wrote: > Well, there was a Bugtraq post today about a S1G bug in MySQL > (and quite possibly other SQL servers as well) and keeping Unix > timestamps in (var)?char fields :) (not that I really understand why > anyone would want to keep a Unix timestamp in a character field..) What's frustrating about the CVSup bug is that it was only "accidentally" an S1G bug. The broken code didn't deal with specifically with dates or timestamps or anything like that. It was a simple text scanning routine, and the bug was a typo in which I typed the name of one variable when I meant to type the name of a different variable. By "luck" (bad luck, that is) this happened to cause no problems until the decimal representation of the date gained a digit. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hubs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200109102011.f8AKBWJ51615>