I am making a database, where a person could track his thoughts, actions and weigh decisions based on pros/cons list.
My thought on structuring the database is to start with person (because it can be multiperson databases solution), so first relationship is
USER::account_created = SESSION::account_created, as I want to store separate sessions, as each session will have 6 digit date code and name.
But here is where I got in trouble. It would be redundant to place thoughts, actions and pros/cons table fields into one field, as 2/3 would be not visible every time. So how can I link 3 different tables: THOUGHTS, ACTIONS, ATTRIBUTES (pros/cons) to SESSION table?
I can only think of having 3 occurencies of SESSION, that is SESSION_THOUGHTS, SESSION_ACTIONS, and SESSION_ATTRIBUTES and then link to respective tables THOUGHTS, ACTIONS and ATTRIBUTES. Any other ideas?
Unless you want to track very different characteristics about a thought vs about an action vs an 'attribute, I would go with one 'what' table and 'action/thought/attribute' becomes just a a 'what type'