Sign in to follow this  
Followers 0
GPT

All Customer's Personal Details in one table or more?

2 posts in this topic

Hello,

 

I have the following tables:

 

CustomerPersonalDetails

ID, Name, Surname, etc.

 

CustomerAccountDetails

ID, UserName, Password, ApplicationDate, RegistrationDate

 

with single and original data,

 

and

 

CustomerEconomicOverview

ID, + Fields with Calculated Data
Custo​merBehaviourOverview
ID, + Fields with Calculated Data

 

with single and calculated data.

 

They all are connected with 1:1 relation.

 

I would like to ask what the suggestable practice is; to keep the data grouped and separated like above or to put them all in one table.

 

Also, my intention is to encrypt all original data.

 

Thanks in advance.

 

 

Share this post


Link to post
Share on other sites

If everything is 1:1 then it's a good idea to put it all in one table. I also don't store calculated values unless I'm only caching them, if I need to calculate a value then I calculate it when I retrieve the row to make sure it's right. There would be a problem if you updated a row somewhere but didn't update the calculated values also, so that they are now wrong.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0