For example storing the different phone numbers that a person might be contacted on. If I do not want my database to be restricted to allow fixed, say 6, numbers per person then the only solution to the problem seems to be to have a separate table and have multiple records for one person.
eg

```
person1, p1number1
person1, p1number2
person2, p2number1
person1, p1number3
.
.
.
...

```

and so no.
But in a practical scenario this kind of table might become very large. So is this approach better or one should not be thinking of storing multivalued attributes in an RDBMS at all?