|
> From: Dave Odom > > As I'm sure you know, however, in order for the iSeries to survive and > compete for dollars against the likes of the real DB2s, Oracle, > SQLServer(I shudder), and the many speciality data warehouse/data mart > implementations, there needs to be a MASSIVE shift in application > development philosophy and attitude in the iSeries community toward door > #2. Why? SQL is simply a tool to access relational data. There is just as valid a reason to shift to completely encapsulated databases and get away from the row/column aspects of SQL. More importantly, the real paradigm shift will be when we design business rules completely devoid of language concerns, be it SQL, RPG or anything else. The next generation of programming will be a combination of a rigorous, platform- and language-independent logic syntax for defining business rules along with UML diagramming for application design. Deployment will be a simple drag-and-drop of portions of the application to the appropriate platform, with a wizard to select the deployment languages as necessary and automatic generation of inter-tier communications. Everyone who is arguing about semicolons and namespaces and triggers and constraints will be out of a job. That won't stop them from arguing, of course; heck, it will mean just as much then as it does now <g>. Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.