3 messages in com.mysql.lists.bugsRe: bug altering default?| From | Sent On | Attachments |
|---|---|---|
| Mikko Lehtonen | 11 Aug 2000 09:47 | |
| Thimble Smith | 11 Aug 2000 15:21 | |
| Michael Widenius | 12 Aug 2000 00:11 |
| Subject: | Re: bug altering default? |
|---|---|
| From: | Michael Widenius (mon...@mysql.com) |
| Date: | 08/12/2000 12:11:32 AM |
| List: | com.mysql.lists.bugs |
Hi!
"Thimble" == Thimble Smith <ti...@mysql.com> writes:
Thimble> On Fri, Aug 11, 2000 at 07:47:48PM +0300, Mikko Lehtonen wrote:
This is my problem:
I made a table with bunch of colums that are the type of text. I noticed that one of them should have default value. I try to correct this by doing this:
-> ALTER TABLE my_table ALTER COLUMN my_column SET DEFAULT "new_default";
and it hung up.. this made me wonder.. I killed my mysqld, and started it from the console and did the same thing again. the server exits with an error "segmentation fault". I did some more testing, and found out that this happens only with the type of text and blob.. (I belive tese are the same)
Thimble> Here's a patch for 3.22.32:
<cut>
Just a last note to Mikko:
All software packages have bugs, especially in code that is not often executed. This particular bug has been with MySQL for 2 years, without anyone noticing or at least reporting it. For all repeatable reported bugs, we create a test case. We run all test cases through every new MySQL release (compiled with purify) to ensure that a bug doesn't come back. When we do a new release, there is no known bugs in it!
We estimate that there is a couple of million MySQL installations and we only get a critical bug report about once in a week, which is usually corrected in a day. I would say this is a pretty good track record!
Regards, Monty