5 Commits

Author	SHA1	Message	Date
cmiller@zippy.cornsilk.net	70802780a5	Merge zippy.cornsilk.net:/home/cmiller/work/mysql/bug20691/my50-bug20691 ... into zippy.cornsilk.net:/home/cmiller/work/mysql/bug20691/my51-bug20691	2006-11-10 14:48:07 -05:00
cmiller@zippy.cornsilk.net	92e0b31978	Bug#20691: DATETIME col (NOT NULL, NO DEFAULT) may insert garbage when \ ... specifying DEFAULT This was not specific to datetime. When there is no default value for a column, and the user inserted DEFAULT, we would write uninitialized memory to the table. Now, insist on writing a default value, a zero-ish value, the same one that comes from inserting NULL into a not-NULL field. (This is, at best, really strange behavior that comes from allowing sloppy usage, and serves as a good reason always to run one's server in a strict SQL mode.)	2006-11-09 18:33:58 -05:00
msvensson@neptunus.(none)	c4b1fb68b4	Bug#10460 SHOW CREATE TABLE uses inconsistent upper/lower case	2006-02-22 10:09:59 +01:00
serg@serg.mylan	86ad035270	test case fixed to pass w/o innodb	2005-09-25 15:44:05 +02:00
mronstrom@mysql.com	5b54fcab6a	Renamed bugs.test to default.test ... Moved enabling of warnings to ensure that no warnings are generated when this test case is executed on a clone where InnoDB is not activated. This would fail the test case in those clones otherwise.	2005-06-01 17:36:21 +02:00