.
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] How do you find out about file operation within an
index?
Thanks for the feed back Phil, but triggers are too slow. We ran a very
simple test and found with triggers, it took 27 seconds to update 5000
records. Without a trigger it took 1 second
Jeff,
TEST.TRIG isn't doing very much, it's writing the same few bytes into the
same bit of memory every time.
What happens if you (re)size JUNK.TRIG to have a modulus of 5000 and change
ID on line 14 of TEST.TRIG to X.
It won't make the trigger run any faster, but it will make TEST.TRIG do a
I'm wondering if there is a way to identify, within a file index, what
type of file operation has occurred.
Hello, Jeff.
Listed below is a program that uses the index like a trigger. It can only
detect WRITE and DELETE statements though. I used this approach with PI and
PI/open as they never
Hi,
If you are talking UV, then triggers will be the quickest option, as
this is done at the database level. You just have to make your code as
efficient as possible. Unfortunately UV does not support a select or
read trigger. When I was in development for VMARK, I argued for it but
alas I was a
You could index an I-type that runs SUBR() to interrogate system variables.
You may need to use FILEINFO() applied to system file variables, if you can
find out what these are called.
Or look at @COMMAND or @SENTENCE, etc.
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe
