Say I have a table with users:
USERS
-----
ID
PASSWORD
CREATED_AT
UPDATED_AT
then I also create a table to track changes:
USERS_LOGS
----------
USER_ID
TIMESTAMP
ID
PASSWORD
CREATED_AT
UPDATED_AT
Does it make sense to have CreatedAt and UpdatedAt on the USERS entity if there is already a "TIMESTAMP" field in USERS_LOGS?
Say I have a table with users:
USERS
-----
ID
PASSWORD
CREATED_AT
UPDATED_AT
then I also create a table to track changes:
USERS_LOGS
----------
USER_ID
TIMESTAMP
ID
PASSWORD
CREATED_AT
UPDATED_AT
Does it make sense to have CreatedAt and UpdatedAt on the USERS entity if there is already a "TIMESTAMP" field in USERS_LOGS?
Say I have a table with users:
USERS
-----
ID
PASSWORD
CREATED_AT
UPDATED_AT
then I also create a table to track changes:
USERS_LOGS
----------
USER_ID
TIMESTAMP
ID
PASSWORD
CREATED_AT
UPDATED_AT
Does it make sense to have CreatedAt and UpdatedAt on the USERS entity if there is already a "TIMESTAMP" field in USERS_LOGS?
Say I have a table with users:
USERS
-----
ID
EMAIL
PASSWORD
CREATED_AT
UPDATED_AT
then I also create a table to track changes:
USERS_LOGS
----------
USER_ID
TIMESTAMP
ID
EMAIL
PASSWORD
CREATED_AT
UPDATED_AT
Does it make sense to have CreatedAt and UpdatedAt on the USERS entity if there is already a "TIMESTAMP" field in USERS_LOGS?
Say I have a table with users:
USERS
-----
ID
EMAIL
PASSWORD
CREATED_AT
UPDATED_AT
then I also create a table to track changes:
USERS_LOGS
----------
USER_ID
TIMESTAMP
ID
EMAIL
PASSWORD
CREATED_AT
UPDATED_AT
Does it make sense to have CreatedAt and UpdatedAt on the USERS entity if there is already a "TIMESTAMP" field in USERS_LOGS?