Designing good data has a fundamental principle of spreading the data out so that each data table stores the information about a particular business entity.
Let’s suppose that the model has a set of restaurants which are located in different cities. Each of these restaurants could have a restaurant ID, the restaurant city and the restaurant state. Another table has a list of workers for the entire restaurant chain with a field indicating which restaurant they are working at. So it is possible to link these two tables based on the common data attribute or field of restaurant ID (in this case).
But sometimes there can be a case that the field in common is having the inconsistent naming and then the data sources will not join automatically. This article aims to explain how to deal with this situation.
Steps to perform:
Whether you're preparing for your first job interview or aiming to upskill in this ever-evolving tech landscape,
GeeksforGeeks Courses are your key to success. We provide top-quality content at affordable prices, all geared towards accelerating your growth in a time-bound manner. Join the millions we've already empowered, and we're here to do the same for you. Don't miss out -
check it out now!
Last Updated :
10 May, 2020
Like Article
Save Article