× 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: Null Capable Fields
  • From: Buck Calabro <mcalabro@xxxxxxxxxxxx>
  • Date: Tue, 12 Oct 1999 15:01:06 -0400

Bruce,
  I was quoting directly from the SQL manual on the "All SQL variables are
nullable" bit.  You are of course 100% correct that you can turn individual
database columns on or off.  As for SQL-language stored procs, I wasn't
talking about stored procs written in RPG or Cobol, I was talking about
stored procs written in SQL (DECLARE PROCEDURE proc () LANGUAGE SQL).  Those
do require C, QM and SQLDK.

I agree again that we should all use embedded SQL, but not all shops are as
forward-looking as you and I, eh?  :-)  It is a bizarre truth that some
places won't spend those few thousand dollars for the SQL development kit on
the "principle" that such an expenditure is overly extravagant.  It's much
easier to qualify the amount of the expense than it is to qualify the amount
of the benefit gained from that expense.

Buck Calabro
Aptis; Albany, NY
mailto:Buck.Calabro@aptissoftware.com

> -----Original Message-----
> From: R. Bruce Hoffman, Jr. 
> Sent: Tuesday, October 12, 1999 1:53 PM
> To:   RPG400-L@midrange.com
> Subject:      Re: Null Capable Fields
> 
> Buck Calabro wrote:
> > 
> > Bruce,
> > Good point, but the original question revolved around work fields, and
> using
> > SQL for work variables is a bit messy, to say the least.  All SQL
> variables
> > are nullable,
> 
> Uhhh.... no. The SQL variable may be nullable, but the SQL columns can
> be set to not allow nulls. If the table came from DDS, the default is no
> nulls.
> 
> > so writing an SQL-language stored procedure may be one way to
> > approach this.  Of course, if one wants to write an SQL-language stored
> > procedure one needs to have the C compiler, DB2 Query manager and the
> SQL
> > development kit installed...  Sigh.
> >
> 
> Again, no. Stored procedures do not require the C compiler. You can
> write them in RPG IV, COBOL, REXX or SQL. Yes, you require the toolkit
> to have the precompilers, but again, in this day and age, why not have
> access to your database through the same interface that virtually ALL of
> the other databases use?
> 
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-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 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.