× 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.



>>c/exec sql
>>c+ set option commit = *none
>>c/end-exec

>When does that drop effect?  At program completion?

As far as I know, it is in effect just for that program.

>Is it just for SQL within that program?

I've never mixed SQL and native access to non-journaled files, but I
strongly suspect that an SQL directive would have no effect on native I/O.

>What if this program calls another SQL program?

I'm not sure if the attribute carries forward into the new program or not.
Because of the way I have to test things, each program needs to stand alone
as much as possible, so all of my SQL programs that do I/O to non-journaled
files have this option set.
  --buck


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.