Re: Object Allocation Problem - or Something Else? -- MIDRANGE-L

Subject: Re: Object Allocation Problem - or Something Else?
From: CRPence <CRPbottle@xxxxxxxxx>
Date: Tue, 21 Feb 2012 13:19:57 -0800
List-archive: <http://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: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On 21-Feb-2012 11:58 , Charles Wilt wrote:

<<SNIP>>

However, on the i, commitment control is only use on SQL DML (data
manipulation language, ie. SELECT, UPDATE, DELETE, INSERT) not on
SQL DDL.

Even if COMMIT(*NONE) affected DDL (as it does on some platforms),
it would just affect the creation of the table, not the functionality
of the table.

The DB2 for i SQL does perform DDL under isolation [commitment control] when established; see SQL0679 for example. However the non-SQL database interfaces do not; instead using a "database recovery" implementation [see CPF3245 for examples of conflicts] to ensure atomicity of the effective DDL.

Regards, Chuck

Follow-Ups:

Re: Object Allocation Problem - or Something Else? , Charles Wilt

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.