RE: QMQRY vs SQL LPP (was: Elementary SQL question) -- MIDRANGE-L

× 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: QMQRY vs SQL LPP (was: Elementary SQL question)
From: Buck Calabro <Buck.Calabro@xxxxxxxxxxxx>
Date: Mon, 24 Sep 2001 09:06:50 -0400
List-Archive: <http://archive.midrange.com/midrange-l/>
List-Help: <mailto:midrange-l-request@midrange.com?subject=help>
List-Id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-Post: <mailto:midrange-l@midrange.com>
List-Subscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=subscribe>
List-Unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=unsubscribe>

>Btw, the qmquery manager does not allow nested functions, eg.
>avg(count(field)). Is this a limitation that does not exist with the
>full blown SQL LPP?

The limitations are the same.  To the best of my knowledge, QMQRY is
essentially an API to the SQL run-time.  That run time comes with OS/400.
The SQL Licenced Program Product adds some front-end type of processing to
give you the interactive prompter (ISQL) and the pre-processors for the
HLLs.

  --buck

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.