4 commits

Author	SHA1	Message	Date
holyfoot/hf@mysql.com/hfmain.(none)	8299b596ae	bug #20691 (INSERT (DEFAULT) may insert garbage with NO DEFAULT NOT NULL field) ... Some fields (GEOMETRY first of all) can't be handled properly in this case at all. So we return an error in this case	2007-02-12 15:41:36 +04: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
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

Renamed from mysql-test/r/bugs.result (Browse further)