sql - Data Base design turnkey records -
i have questions regarding data base design simple cms.
every page in table "pages" "assignedto" , "lockedby" specific user. manage users using sql specific table "aspnet_users", every user identified using gui uniqueidentifier column.
if page "unlock" , can edited users, value in table "pages" null, same mechanism "assignedto".
here script when create table "pages":
lockedby uniqueidentifier null foreign key references aspnet_users(userid), assignedto uniqueidentifier null foreign key references aspnet_users(userid)
my question: design generate many null values in "lockedby" since pages locked in moment of editing, because heard have many null values not thing in data base design,, know if design in practice, or if suggest better way. guys
normally think it's idea have in 1 table, ignoring fact there's many null values, here's solution:
you split 2 other tables: pagelocks , pageassignedto
pagelocks: pageid, userid <- unique key
pageassignedto: pageid, userid <- unique key
Comments
Post a Comment