× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: What About Price vs. Performance?
  • From: "Joe Pluta " <joepluta@xxxxxxxxxxxxxxxxx>
  • Date: Thu, 5 Apr 2001 11:10:34 -0500

SQL is without a doubt the single worst way for a client to access a host 
database.  Because it requires in-depth knowledge of not only the location but 
the format of the data, it ties the host to the client irretrievably.  Any 
change to the database layout requires an immediate and complete upgrade to 
every client.  A message-based architecture, on the other hand, allows 
independence of client and host, and can also support deprecated messages, 
allowing clients to upgrade in a more convenient timeframe.

But that's just my opinion.  If they ever get OQL working, I'll be a happy man. 
 Until then, I'll stay message-based, thank you.

Joe


---------- Original Message ----------------------------------
From: "Stone, Brad V (TC)" <bvstone@taylorcorp.com>
Reply-To: MIDRANGE-L@midrange.com
Date: Thu, 5 Apr 2001 10:30:50 -0500 

>> No, if you have something better than the AS/400, go ahead.  
> In the meantime, I'll use the best tool for the job, and if 
> the time comes to find another server, I'll simply redesign 
> my templates and move on.  Remember, Leif, all of my servers 
> are encapsulated by a message, so they can be reimplemented 
> in any language on any platform I choose.  I simply choose 
> the AS/400, and have no reason to be "free" of it.
> 

One more thing.  Which is the lesser of two evils?  Using SQL for record
access, or using messaging?  In one case all you should need is possibly a
new JDBC driver.  In the other, your back end data mining tools (in your
case I believe written in RPG) have to be rewritten.

I see advantages to each, but I think I would choose the SQL route.

Then again, that assumes that table and DB layouts remain unchanged when you
move to the new platform (of course).

Brad
+---
| 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
+---

+---
| 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 thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.