HelperT is a great solution. Now I hope in later lessons you will consider the means by which various T's can be consolidated into an EntityT. I have one Database in which I have Contestants, Teachers, Schools, and residents of the town all in separate T's. And some of them are in more than one T. I see a myriad of problems. Hope you have the roadmap that avoids them.
Sure. Just make a field called EntityTypeID. That itself could be stored in the HelperT. This would allow you to distinguish between customers, employees, residents, etc. I am going to be creating a grouping and classification system coming up very soon where you can add people to one or more groups. That will most likely be in Part 2.
Julian Okolonji
@Reply 5 years ago
Hi Richard thanks for your good works. Does it mean that at this point we can go ahead and create the EntityTypeID for ourselves even with Groups already created to enable relationship between EntityTypeID (Ts) or are you planning on including it in future modules.
If you are a Visitor, go ahead and post your reply as a
new comment, and we'll move it here for you
once it's approved. Be sure to use the same name and email address.
This thread is now CLOSED. If you wish to comment, start a NEW discussion in
ABCD.
