|
FoxDataObjects |
Object-Relational Mapping Tool for Visual FoxPro® |
|
|
AutomaticTransactions Property |
||
|---|---|---|
|
Determines whether the persistence engine will start a new transaction when a persistence method runs and there is no active transaction.
|
|||||||||
|
Property Values |
|||||||||
|
lValue |
|||||||||
|
|||||||||
|
Remarks |
|||||||||
| When this property is set to .T. ,
the Session.SaveObject and Session.DeleteObject methods will
start a database transaction automatically before sending any database
command, if no transaction is active. Once the transaction has been
initiated, SaveObject and DeleteObject methods will send the proper SQL
Insert/Update and Delete commands to the database in order to persist/remove
the object graph. At the end, the transaction will be committed. When this property is set to .F., the Session.SaveObject and Session.DeleteObject methods never start or commit any database transaction. All transaction demarcation commands must be manually issued using the Session.Transaction object. Note: When a group of objects must be updated/deleted out of a persistence event, and all data changes must be protected by the same database transaction, then a manual transaction begin demarcation must be issued before calling the first persistence method. It is not necessary to disable AutomaticTransactions. Finally, when all objects has been persisted, the transaction can be committed using the Session.Transaction.Commit method. Use this property when transaction management is done outside FoxDataObjects.
|
|||||||||
|
See Also |
|||||||||
|
Server.NewSession method | Session.Connect method | Session.Transaction object |
|||||||||
| Applies to: Server object | |||||||||
|
Send feedback on this topic to RunAhead Technologies For Technical support and product issues please contact us at support@foxdataobjects.com or visit http://www.foxdataobjects.com |
Copyright (c) 2000-2005 RunAhead Technologies