On 5/17/2013 2:05 PM, Michael Haberler wrote: > that said, what I am convinced is needed is proper design work on a > relational_model_ for the tool miniworld (tools, offsets, spindles, > magazines, wear, holders and whatever came up over the years) > > <...> > > As for an OODB approach - I never understood what that is so I cant comment, > but it surely doesnt get us around the legwork designing a bulletproof data > model
"My bad" for saying RDB and OODB as a shorthand for the conceptual models and methodologies that back the design of RDBs and OODBs. I could not agree more strongly with the need for proper design. Speaking in database-ese, the availability of two different data models (relational vs O-O) means one might choose slightly different approaches to that design even at the conceptual schema level but certainly will choose differently at the logical schema level (ANSI/SPARC defined the three-schema approach back in 1975). This does not remove the need to state clearly the purpose of the database and to gather and massage end-user requirements. I think we are assuming we've agreed the purpose of "the database" and I'm sure that many of Chris Morley's emails contain end-user requirements which need to be captured. Regards, Kent ------------------------------------------------------------------------------ AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
