I'll swap you the designers who worry about the form of their database model/design for ours that have none at all. todays special. skills 'database'. two tables skills_header skills_detail (skill_id,staffno,skill_level,... ) - . skills_header contains only staff details no skill information at all - *that *is held on a filesystem in XML. On 6/14/05, stephen booth <stephenbooth.uk@xxxxxxxxx> wrote: > > On 14/06/05, Post, Ethan <Ethan.Post@xxxxxx> wrote: > > Actually as I understand it Einstein was not all that great at math > > either, but he had the ability to conceptualize things that no one else > > could. I believe you can be a pretty good DBA and not really be great at > > math. > > Thinking of some of the systems we've had put in by suppliers and the > conversations I've had with their design/development people, I suspect > that some people in the field (quite a lot of them actually) worry > more about how elegantly they can describe the data model in > mathematical terms and not so much about "Will it work?" There was a > similar culture going around when I used to be a C developer. > > I think there has to be a balance between producing pretty diagrams > and producing a system that will actually fulfil the spec and do what > it's supposed to do. > > Stephen > > --=20 > It's better to ask a silly question than to make a silly assumption. > -- > //www.freelists.org/webpage/oracle-l > -- Niall Litchfield Oracle DBA http://www.niall.litchfield.dial.pipex.com -- //www.freelists.org/webpage/oracle-l