On 4/1/2014 5:01 PM, Steve Newcomb wrote:
That's why a good data model is essential, especially one that includes some of the context. It's only later that the time comes to choose xml (or not) for interchange, or table design for the database.(e) There is no "getting it right". There is only fitness for purpose in context. Change the purpose and/or the context, and it's usually wrong. Even (actually, especially) at the table level. A table is inevitably and inextricably bound to a perspective.