RE: Embedded SQL weirdness

[Mark Lazarus <mlazarus@xxxxxxxx>]

Chris,

At 04:55 PM 1/14/99 -0800, you wrote:

>> 2)  If the program is not under commitment control but the program is
>> compiled with the default COMMIT( *CHANGE ), should this affect
>> the results
>> of the update?

>I believe the delete will not occur unless you explicitly 'Commit' in the
>SQL. If you do not need Commitment Control, the best way to avoid having to
>create a journal, etc., or continuously set the COMMIT parameter on the
>CRTRPG, is to simply append 'WITH NC' to the DECLARE, DELETE, INSERT, or
>UPDATE statement. This also makes it clearer to future programmers what your
>intentions were.

 Thanks for the explanation.  Although I wish that the compiler or even the
runtime environment would recognize that committment control is not active
and behave accordingly.

 -mark

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