jimw@mysql.com
a35c324358
Fix over-optimization that could result in an unsigned double field being
...
set to a negative value. (Bug #7700 )
2005-01-17 16:13:56 -08:00
monty@mashka.mysql.fi
9fb7e863ad
Optimized old patches
...
Don't set field to DEFAULT value when set to NULL
2003-07-01 14:38:38 +03:00
hf@deer.(none)
3007290f83
Another bugfix for #615
...
Looks a bit nicer than previous one
2003-06-24 10:53:21 +05:00
hf@deer.(none)
eb901ea461
Proposed fix for #615
...
So now for the CREATE TABLE foo (id integer NOT NULL default 9)
INSERT INTO foo VALUES (NULL); we get an error
INSERT INTO foo VALUES (1), (NULL), (2); we get one warning
and second record is set to 9
Is that what we want?
2003-06-20 18:52:40 +05:00
monty@mashka.mysql.fi
8dd439e751
Guard against compiling without -fno-exceptions
...
Allocate bigger default thread stack because of problems with glibc
Fixed bug in UPDATE ... not_null_field=expression_that_returns_null
Fixed bug in replication when using auto_increment and LOAD DATA INFILE
2003-01-14 11:27:26 +02:00
monty@hundin.mysql.fi
8830eb4aa9
Change of internal key_field=NULL handling to avoid error messages.
...
Optimized SELECT DISTINCT ... ORDER BY ... LIMIT
Fixed reference to uninitalized variable
2002-12-03 13:08:25 +02:00
monty@hundin.mysql.fi
67d3cd643b
Merge with 3.23.54
2002-10-16 13:11:25 +03:00
monty@hundin.mysql.fi
b4343ba939
Fixed bug in LEFT JOIN ... WHERE not_null_key_column=NULL;
2002-10-16 10:32:45 +03:00
monty@hundin.mysql.fi
b658662ae4
Update copyright
...
Fixed memory leak on shutdown (Affects the embedded version & MyODBC)
2001-12-06 14:10:51 +02:00
monty@donna.mysql.fi
32d403f087
Fixed bug in INSERT DELAYED when INSERT generated an error
2001-03-08 21:49:15 +02:00
bk@work.mysql.com
f4c589ff6c
Import changeset
2000-07-31 21:29:14 +02:00
