|
Rob, You wrote: "What 'back door' were you thinking of?" The ability to get to supposedly a relational database via access verbs such as READ, WRITE, etc. If the iSeries were truly relational, that would not be allowed. "I didn't understand the last two sentences." I'm not sure which ones to which you are referring. "Are you trying to say that any file access, outside of imbedded SQL, is what makes it non relational?" I'm not comfortable with the term "imbedded SQL" as that implies to me imbedded in a program, but the simple answer is Yes, a truly relational database must only be accessed via one language, in all cases, and in the truly relational world, the defacto is SQL. "And this is a bad thing?" Yes, it violates the essence of what Codd was saying, and what he was saying was often oriented toward what is best for good database and application development architecture for the near and long term. To wit..., allowing multiple access verbs and paths, does not conform to the rest of the truly relational world if you want applications built that are compatible with other relational database engines your company might need to consider and for which there is a good supply of traditionally trained employees in relational database and application design. I don't know about you but business leaders I've consulted with don't like having an environment that is not flexible thus making things harder when it comes to M&A activity or expansion or downsizing.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.