Support Forums - View Thread

View Thread

The following is the text of the current message along with any replies.

Messages 11 to 14 of 14 total

Check if tables are updated in transaction

Wed, Sep 16 2015 11:56 AM	Permanent Link
Matthew Jones	Roy Lambert wrote: > you should never have user input as part of a transaction. Wasn't it an ambulance system that locked records and then stopped any action on it when people went to lunch? Some hoo-hah on that IIRC. -- Matthew Jones
Wed, Sep 16 2015 2:47 PM	Permanent Link
Mike	Thanks (both) for the explanation. There is only one user. Would this also be a problem?
Thu, Sep 17 2015 7:24 AM	Permanent Link
Roy Lambert NLH Associates Team Elevate	Matthew >Wasn't it an ambulance system that locked records and then stopped any >action on it when people went to lunch? Some hoo-hah on that IIRC. Not something I remember but given the state of most governmental IT projects highly likely. Roy
Thu, Sep 17 2015 7:25 AM	Permanent Link
Roy Lambert NLH Associates Team Elevate	Mike >There is only one user. Would this also be a problem? If there's only one user then no - after all the only user that he/she would be able to lock would be themselves. However, it would be better programming practice to ask if the user wanted to bother saving stuff. If not why go though a save into memory then throw it away approach (which is essentially what a transaction and rollback does). Roy Lambert

« Previous Page	Page 2 of 2
Jump to Page: 1 2