|
I've never done a DS for the whole record on an update. Do you have the SQL code that occurred? ncsmith@gate.net on 07/16/99 12:50:04 AM Please respond to RPG400-L@midrange.com@Internet To: RPG400-L@midrange.com@Internet cc: Fax to: Subject: Re: RPG SQL precompiiler An individual host variable for a field works ok on Update statements, but I have not been able to get an externally defined data structure to work so I could update an entire record at once instead of having to list each field separately. Have you? Maybe I'm just doing something wrong. The externally defined ds works fine for Inserts and Selects. I just haven't been able to get it to work for Updates. Also, I have never found an example of such in any SQL book or IBM manual. -----Original Message----- From: Rob Berendt <rob@dekko.com> To: RPG400-L@midrange.com <RPG400-L@midrange.com> Date: Thursday, July 15, 1999 11:04 AM Subject: Re: RPG SQL precompiiler >I don't understand your question. Are you saying that we >can't do the following: > >update filea > set qty=:qtyonhand > where itemnum=:partno > >And on the other part - about adding non standard SQL features. >I'd just as soon IBM try to get the standards bodies to accept >it first, within reason. > > > > > >ncsmith@gate.net on 07/15/99 12:50:18 AM >Please respond to RPG400-L@midrange.com@Internet >To: RPG400-L@midrange.com@Internet >cc: >Fax to: >Subject: Re: RPG SQL precompiiler > > >Also, a general question I have for the developers is: > >If I can Insert from a host variable and select into a host variable, why I >can't I update from a host variable? > >I know the answer is probably going to >be because normal SQL doesn't support it, but what is normal about our >precompiler? As long as it is embedded into RPG anyway, it certainly isn't >going to be used anywhere else, so why can't we have some additional >functionality added to it. >* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * >* This is the RPG/400 Discussion Mailing List! To submit a new * >* message, send your mail to "RPG400-L@midrange.com". To unsubscribe * >* from this list send email to MAJORDOMO@midrange.com and specify * >* 'unsubscribe RPG400-L' in the body of your message. Questions should * >* be directed to the list owner / operator: david@midrange.com * >* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * > * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This is the RPG/400 Discussion Mailing List! To submit a new * * message, send your mail to "RPG400-L@midrange.com". To unsubscribe * * from this list send email to MAJORDOMO@midrange.com and specify * * 'unsubscribe RPG400-L' in the body of your message. Questions should * * be directed to the list owner / operator: david@midrange.com * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This is the RPG/400 Discussion Mailing List! To submit a new * * message, send your mail to "RPG400-L@midrange.com". To unsubscribe * * from this list send email to MAJORDOMO@midrange.com and specify * * 'unsubscribe RPG400-L' in the body of your message. 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.