Re: sql and commitment control -- MIDRANGE-L

Subject: Re: sql and commitment control
From: Steve Richter <stephenrichter@xxxxxxxxx>
Date: Wed, 14 Mar 2018 16:09:59 -0400
List-archive: <https://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: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On Wed, Mar 14, 2018 at 4:02 PM, Charles Wilt <charles.wilt@xxxxxxxxx>
wrote:

I think the issue is the ATOMIC .... I believe that starts a commit
definition implicitly. As there's no way for the DB to do guarantee
consistency otherwise.

try changing ATOMIC to NOT ATOMIC...

excellent! thanks.

This mailing list archive is Copyright 1997-2026 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.