Commit Control
-
devinst
- Profound User
- Posts: 80
- Joined: Mon Apr 20, 2009 11:26 am
- First Name: Devin
- Last Name: St. Germain
- Company Name: Dupre Logistics, LLC
- Phone: 337.314.2259
- Address 1: 201 Energy Pkwy. Ste. 500
- City: Lafayette
- State / Province: Louisiana
- Zip / Postal Code: 70508
- Country: United States
- Contact:
Commit Control
When using Database Driven Selection in a selection box, does Profound UI use SQL to populate the object? If so, where does it get its commit control level? Will it pick up the same option as used in the controlling RPG object? Thanks.!!!
-
Scott Klement
- Experienced User
- Posts: 2711
- Joined: Wed Aug 01, 2012 8:58 am
- First Name: Scott
- Last Name: Klement
- Company Name: Profound Logic
- City: Milwaukee
- State / Province: Wisconsin
Re: Commit Control
It generates an SQL SELECT statement, and runs it using the SQL Call-Level Interface (CLI). It does not set any commitment control settings, so it'll end up with whatever is the default for SQL CLI. I believe the default is SQL_TXN_READ_UNCOMMITTED.
Why, is this causing you problems?
Why, is this causing you problems?
-
devinst
- Profound User
- Posts: 80
- Joined: Mon Apr 20, 2009 11:26 am
- First Name: Devin
- Last Name: St. Germain
- Company Name: Dupre Logistics, LLC
- Phone: 337.314.2259
- Address 1: 201 Energy Pkwy. Ste. 500
- City: Lafayette
- State / Province: Louisiana
- Zip / Postal Code: 70508
- Country: United States
- Contact:
Re: Commit Control
We were having trouble with our backups and I just wanted to rule that out. I have begun using some commit control in our development, *CHG, and wanted to make sure that it would not be an issue. Thanks for the info.!!!
Who is online
Users browsing this forum: No registered users and 6 guests