|
From: Phil Groschwitz <sublime78ska@yahoo.com> > Would using jdbc and stored procedures also isolate > the client code from the database logic? Then it > wouldn't matter whether the stored procedure was RPG > or sql or cobol, on an as/400 or oracle? > > I'm not saying, or asking, which is better - I'm > asking which is truly most portable. as long as you put all that behind an interface (or as Joe would say: a message, or as OO people would say: a method) hidden from the application code, it is portable. NEVER embed SQL. JDBC, ODBC, what have you, directly in your application code. +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.