Dear Imar,
I am back after a great amount of time. But when I got back to your book then I had few questions in mind.

We have been using normalization. We store Id of any element rather its name, so that it could be reflected quickly in dependent tables when ever there is change in name of that element.
But I wanna ask that why you have not stored UserId in the PhotoAlbum table in place of OwnerName (user name)? However there is no need to change user name but no every boss is same.
So is storing UserId not convenient? What you recommend strongly and why?

Thanks in advance.

Hi there,

Yes, you're absolutely right. It would make a lot of sense to use the ID so you can link the two records to each other.

However, at the stage where you implement this feature in the Planet Wrox site, the photo album and the use are stored in two separate databases. This makes it difficult to display the user's name along with the album as you need to do a join between two databases. Only in the last chapter are the two databases merged into a single one, enabling the scenario you're describing.

So, if you have a single database, storing just the user id pointing back to a Users table absolutely makes sense.

Cheers.

Imar

__________________
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Follow me on Twitter

Author of Beginning ASP.NET 4.5 : in C# and VB, Beginning ASP.NET Web Pages with WebMatrix
and Beginning ASP.NET 4 : in C# and VB.
Did this post help you? Click the button below this post to show your appreciation!

Hi Imar,

thanks for your response. I will check the last chapter again to have a clear view of joining two databases.

Once again thanks and best of luck with your recently opened new company...