> If you’ve already decided that you have to have an RDBMS to clear the job, take this advice: screw the good advice ‘never design for the future’. This gives

> If you’ve already decided that you have to have an RDBMS to clear the job, take this advice: screw the good advice ‘never design for the future’. This gives a high expectancy for the article. It begins in a good way, with a real database, but all of sudden it ends. Some questions are presented, but I'm sure it will get much more valuable when the problems are solved by showing the answers and examples. Probably a following article will complement it, no?