I've got a table
users and a table
bookmarks. The table
bookmarks obviously contains pages the user wants easy access too.
But, there's a new requirement now: every user gets 3 unmutable bookmarks. One of the bookmarks (be it an unmutable one or a user-specific one) is marked as homepage. Always.
I'm thinking about 2 solutions, but I'm not sure which one to choose:
1) Add those 3 records for every user and use triggers or application logic to enter those 3 records automatically when a new user is created.
2) Keep those 3 'records' out of the database altogether and fix it in the application (on the 'bookmarks' page). This solution has a great disadvantage: by default, one of the 3 unmutable bookmarks is selected as the user's homepage. The user can change their homepage to one of the other 2 unmutable bookmarks, or a bookmark of their own. I would have no place to store this data, or I would have to insert the 3 unmutables in case the user makes a change. But that sounds hackish.
What would you do? Is inserting 3 records for all users a design flaw?