Re: MATREADU/MATWRITE statements timing out
- From: "Excalibur" <excalibur21@xxxxxxxxxxx>
- Date: Fri, 23 Nov 2007 21:11:28 GMT
Hi Mike
Thanks. My initial experience was based on actual timings taken of how
often a record got hit on a Reality when I had a screwed up record. Of
course what had happened was an order entry clerk had an issue during a
telephone call, she called across the room to get help, 2nd party promptly
brought it up on screen and then telephoned through to credit control who
promptly did the same thing. One or even two of them then made changes but
all three filed the record even though they had a clear entry key. An audit
trail record showed that this scenario was frequent and the hits were all in
under 3 seconds. Funnily enough this is the scenario suggested by another
post as not needing a lock!
By the way I do have time out retries etc as I call a standard Lock routine
with a variety of options. The only place I can see where it is possibly
overkill is when returning a list of items based on an enquiry. However
even there it is debatable as a person will normally be making a selection
from the list and will need to know about changes, locks etc.
In my opinion the appropriate answer is to provide a LOCKED clause on the
READ but I am told by the suppliers that I am wrong so I do it my way.
Regards
Peter McMurray
"Michael Findlay" <michael@xxxxxxxxxxx> wrote in message
news:26e5449e-41ea-459d-8e5f-45930a7892cc@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Nov 23, 8:46 am, "Excalibur" <excalibu...@xxxxxxxxxxx> wrote:news:070f5dee-c9f8-4051-a81b-54a755733a1a@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
"Kevin Powick" <kpow...@xxxxxxxxx> wrote in message
On Nov 22, 2:58 am, "Peter McMurray" <excalibu...@xxxxxxxxxxx> wrote:
the
Why would anyone ever write a READU instruction on a
multi-user system without a LOCKED clause? In 30 years it has never
occurred to me to do such a thing.
I don't know about Universe, but for Pick versions, the LOCKED clause
has not been around for 30 years.
Ah Mea Culpa. I should have said 20 years, I see that I pencilled in
satchange on my Pick Pocket Guidearound 1988. Before that I suppose I just
whenand let it scream, unfortunately I cannot check as I updated everything
surprisedI fixed Year 2000 or rather Day 10000 around 1988. However I am
well Ithat I never ran into the issue anywhere.
In fact I just avoid the plain READ
because it does not have a LOCKED option.
I think that is a little extreme. There is no reason to abandon the
standard READ statement. IMO, the only time one should consider
locking a record in the first place is if they might be updating that
record.
Yeah! I tend to agree but the solution of READ and RELEASE works so
have not rushed to change it.
Peter McMurray
--
Kevin Powick- Hide quoted text -
- Show quoted text -
Hey Peter
I tend to have to agree. I never used to use the locked clause back in
my early days (excuse my age, 26 and been on pick for around 8 years
in the industry) probably due to lack of knowledge, but it is soo much
easier and interactive when you can alert the user who is currently
holding the lock on the record they are trying to access, or skip a
record in a batch update and come back to it later.
I did test the readu on universe 9.2 and sure enough, on with the else
clause after around an hour or so when reading. Can't believe the DB
would allow that, splat to the data hey.
Locking records is essential in any system where a user can sit in a
record for a period of time, then update the data and write it back to
the database. If there is no locking, what is to stop 4 users altering
the record in the time user A is viewing it....then user A saving his
record away and killing the last 4 updates????? Crazy.
Mike
.
- References:
- MATREADU/MATWRITE statements timing out
- From: mattydp
- Re: MATREADU/MATWRITE statements timing out
- From: Peter McMurray
- Re: MATREADU/MATWRITE statements timing out
- From: Kevin Powick
- Re: MATREADU/MATWRITE statements timing out
- From: Excalibur
- Re: MATREADU/MATWRITE statements timing out
- From: Michael Findlay
- MATREADU/MATWRITE statements timing out
- Prev by Date: Re: MATREADU/MATWRITE statements timing out
- Next by Date: Re: MATREADU/MATWRITE statements timing out
- Previous by thread: Re: MATREADU/MATWRITE statements timing out
- Next by thread: Re: MATREADU/MATWRITE statements timing out
- Index(es):
Relevant Pages
|