Problems Cause by DB Relationships

I created what feels like a parent-child relationship from a parent TimeZone table to the child User table.
I want the user to choose their time zone and store that in the user table with their other data.

What I’m afraid is this approach, that is having a column in a child table whose data type is the parent table, is going to MESS UP something either in the UI, or workflow or creating or updating records or something…

See the attache picture


Why would you expect any problems with it? This will literally have 0 impact on anything until you actively use it.

This topic was automatically closed after 70 days. New replies are no longer allowed.