new SQL keyword: might-be
Have you ever known someone who still confuses relational databases with flat file structures? Someone that would rather have the application define data relationships than constrain them in the database? I would like to propose a compromise with those people by introducing a new sql keyword. Take a look at the new might-be constraint:
alter table SCHEMA.MY_TABLE add might-be constraint MY_TABLES_FK foreign key (ASSIGN_ID) might reference SCHEMA.OTHER_TABLE(ID);
Labels: Programming