Bugs item #1997030, was opened at 2008-06-18 18:40 Message generated for change (Settings changed) made by mlkersten You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=482468&aid=1997030&group_id=56967
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: SQL/Core Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Sam Mason (sam_mason) Assigned to: Niels Nes (nielsnes) >Summary: SQL: NOT NULL constraint is not checked when applied to Initial Comment: As far as I'm aware the SQL spec requires the RDMS to verify that data already existing within a table is valid when applying new constraints. This check currently appears to be missing from monetdb. CREATE TABLE foo (i INT); INSERT INTO foo (i) VALUES (NULL); ALTER TABLE foo ALTER COLUMN i SET NOT NULL; I'd expect this last command to fail. Running INSERT again causes monet to recognize the constraint but only for the new data. SELECT i FROM foo; verifies that there is a null value still in the column. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=482468&aid=1997030&group_id=56967 ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Monetdb-bugs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/monetdb-bugs
