Probably read committed.
On Feb 27, 2:01 pm, DenesL <denes1...@yahoo.ca> wrote:
> Massimo, which setting would you recommend in the ODBC DSN?
>
> Commit modes
>
> These are default commit modes that will be used if the application
> does not specifically set them.
>
> Commit immediate (*NONE)
>
> Specifies that commitment control is not used. COMMIT and ROLLBACK
> statements are not allowed. Uncommitted changes in other jobs can be
> seen. If the SQL DROP COLLECTION statement is included in the program,
> *NONE must be used. If a relational database is specified on the RDB
> parameter and the relational database is on a system that is not an
> iSeries, *NONE cannot be specified.
>
> Read uncommitted (*CHG)
>
> Specifies the objects referred to in SQL COMMENT ON, CREATE, DROP,
> GRANT, LABEL ON, and REVOKE statements and the rows updated, deleted,
> and inserted are locked until the end of the unit of work
> (transaction). Uncommitted changes in other jobs can be seen.
>
> Read committed (*CS)
>
> Specifies the objects that are referred to in SQL COMMENT ON, CREATE,
> DROP, GRANT, LABEL ON, and REVOKE statements and the rows updated,
> deleted, and inserted are locked until the end of the unit of work
> (transaction). A row that is selected, but not updated, is locked
> until the next row is selected. Uncommitted changes in other jobs
> cannot be seen.
>
> Repeatable read (*ALL)
>
> Specifies the objects referred to in SQL COMMENT ON, CREATE, DROP,
> GRANT, LABEL ON, and REVOKE statements and the rows updated, deleted,
> and inserted are locked until the end of the unit of work
> (transaction). Uncommitted changes in other jobs cannot be seen.
>
> Serializable (*RR)
>
> Specifies the objects referred to in SQL COMMENT ON, CREATE, DROP,
> GRANT, LABEL, ON, and REVOKE statements and the rows updated, deleted,
> and inserted are locked until the end of the unit of work
> (transaction). Any row read during a unit of work is not changed by
> other activation groups that use different commitment definitions,
> until the transaction is complete. Any row changed (or a row that is
> currently locked with an UPDATE row lock) by another activation group
> using a different commitment definition cannot be read until it is
> committed.
>
> In addition to any exclusive locks, an activation group running at *RR
> acquires share locks on all the rows it reads. The locking is
> performed so that the activation group is completely isolated from the
> effects of concurrent activation groups that use different commitment
> definitions.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py Web Framework" group.
To post to this group, send email to web2py@googlegroups.com
To unsubscribe from this group, send email to
web2py+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
