|
Paul, These statements are incorrect: "Eight because an underlying change to the database will require changes to RPG programs. If the sequence of fields in a table are changed or length of fields changed the RPG program must be modified to deal with the database change. No so with SQL. SQL doesn't care that that column is the first column in the table. "Having said all that, if you stick strictly to SQL for all your database access then the AS/400 database is a relational database. Until DB2/400 prevents access to the database outside of SQL it's not strictly relational." You are confusing an applications programming issue with a database management issue. With SQL Server table "blah" with field1, field2, field3, write an ASP page with "select * from blah". Process the fields by ordinal. The program assumes fields(0) is field1. Now, reorder the fields to be field3, field2, field1. Re-run the ASP script. What is fields(0)? It's now field3. Is that the fault of SQL server? No. But by your logic, SQL server isn't relational because changes to the structure require ASP application changes. I used solely SQL to access the data. The fault is with SELECT *, and that is an applications issue, not a database issue. Loyd Goodbar Senior programmer/analyst BorgWarner E/TS Water Valley 662-473-5713
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.