To Asvin, you cannot set locks in the same sequence every time.
This is because, in a sufficiently complex system you will have
changes to Customer's possibly affecting Orders, Inventory, Payables...
You can then have changes to Inventory possibly affecting Orders,
Customers,
that time period.
Asvin wrote: Big grin - how do you do that in internetese?
-Original Message-
From: asvin.dattani asvin.datt...@hsbcib.com
To: U2 Users List u2-users@listserver.u2ug.org
Sent: Thu, Oct 27, 2011 2:36 am
Subject: Re: [U2] Avoiding deadly embraces
To Asvin, you cannot
Subject: Re: [U2] Avoiding deadly embraces
To Asvin, you cannot set locks in the same sequence every time.
This is because, in a sufficiently complex system you will have
changes to Customer's possibly affecting Orders, Inventory, Payables...
You can then have changes to Inventory possibly
Subject: Re: [U2] Avoiding deadly embraces
I think Asvin means this ;D
On 27/10/2011 17:33, Wjhonson wrote:
First explain what you mean, then I can answer it.
How do I do what?
Will wrote: It seems like some of you have only ever worked on rather simple
systems, built by yourselves
Hi,
You can avoid a deadly embrace if you can arrange it so that all processes
lock related tables/files in the same sequence.
Take the example of a system with a CUSTOMER file, a ORDER HEADER file and
an ORDER DETAILS file. If some processes lock the ORDER HEADER file first
and the CUSTOMER
I find the best practice is to try and lock and read all the necessary
components before the first update. That way if an item we need to update
as we go along is unavailable we catch it up front and don't get stuck.
Or if you have TRANSACTION PROCESSING in place you can just to an ABORT.
I
-users@listserver.u2ug.org
Sent: Wed, Oct 26, 2011 6:42 am
Subject: Re: [U2] Avoiding deadly embraces
I find the best practice is to try and lock and read all the necessary
omponents before the first update. That way if an item we need to update
s we go along is unavailable we catch it up front
What do you think I am doing day in day out?
I work with Avante 9.2 from Epicor and I definitely didn't write that
myself.
And this isn't the first system I've worked with in nearly 25 years in
the MV world.
And to be honest I have barely scratched the surface of Avante since I
only look at
-
From: David A. Green dgr...@dagconsulting.com
To: 'U2 Users List' u2-users@listserver.u2ug.org
Sent: Wed, Oct 26, 2011 6:42 am
Subject: Re: [U2] Avoiding deadly embraces
I find the best practice is to try and lock and read all the necessary
omponents before the first update. That way
sequence in every
case, illustrates the communication divide.
-Original Message-
From: Brian Leach br...@brianleach.co.uk
To: U2 Users List u2-users@listserver.u2ug.org
Sent: Wed, Oct 26, 2011 2:47 pm
Subject: Re: [U2] Avoiding deadly embraces
Will - you couldn't be more wrong in your
10 matches
Mail list logo
