I would have to disagree with "learning newbie", you should always draw out your database design structure before you ever create a table. Using this method, you'll be able to spot things such as redundancy. It takes time to develop the ability to draw these out, start by getting as much information about your data as possible. Understand what data relates to each other and then get yourself a really big white board and draw out your ER Diagram.
You have a valid point, but I'd argue a person doesn't need to draw a design structure on paper first. A person who's trained themselves to think in these terms, in the relational model. You don't have to look at redundancy to be aware of it.
__________________
Chris. ->> Links are advertising NOT optimising!! <<-
A foolish consistency is the hobgoblin of little minds
Thought for today:- I SEO the only industry where all the cowboys are Indians?
Wouldn't you be better looking at how it has been done previously by fellow employees as there may be a company standard to follow.
Other than that, given your example it's simply a description of the data in each field.
__________________
Chris. ->> Links are advertising NOT optimising!! <<-
A foolish consistency is the hobgoblin of little minds
Thought for today:- I SEO the only industry where all the cowboys are Indians?
Ah, I see. So it's not the database or schema or whatever you're looking for info on, it's the finance side of things? 'Cause knowing that we'll be able to patch together a useful answer.
not really, because as previously noted you need to be asking someone who is in the same field
__________________
Chris. ->> Links are advertising NOT optimising!! <<-
A foolish consistency is the hobgoblin of little minds
Thought for today:- I SEO the only industry where all the cowboys are Indians?