Jeff, I cannot see how you can do it any quicker? The only thing you could hope for is that IBM look at how they call they trigger subroutine, (while they are fixing the issue with the debugger - my personal battle...:-) ), as whatever basic code you come up with to capture the information will be the same as what you put in the trigger. The advantage of the trigger is that you are assured that it will be executed....
Maybe you can check your code to see how efficient it is in doing writes. Hopefully it is only doing the write once, and not repeatedly doing the writes or writevs..... as this will indeed cause the trigger to fire more than once. The other thing to do with the trigger code is to open the 'log' file variable into common, and be very efficient in what you are doing... Do not take this as a criticism of your code, as without seeing it, noone could say. But as the code is going to be called every time the database does a write or a delete then it needs to be efficient. Cheers, Phil. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Marcos Sent: Thursday, 11 May 2006 12:31 p.m. 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... Regards, Jeff Marcos This e-mail is for the use of the intended recipient(s) only. If you have received in error, please notify the sender immediately and delete it. If you are not the intended recipient, you must not use, disclose or distribute this e-mail without the author's prior permission. Corporate Express checks all outgoing mail and accepts no liability for any loss or damage caused by software viruses. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of phil walker Sent: Thursday, 11 May 2006 9:06 AM To: u2-users@listserver.u2ug.org Subject: RE: [U2] How do you find out about file operation within an index? 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 lone voice..... Cheers, Phil. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Marcos Sent: Thursday, 11 May 2006 11:01 a.m. To: u2-users@listserver.u2ug.org Subject: [U2] How do you find out about file operation within an index? Hello all, I'm wondering if there is a way to identify, within a file index, what type of file operation has occurred. Example; we have a program in an index to do some checks. We would also like to find out, what the user is doing; delete, write, read, readu, etc,... Using triggers is not an option, because it just way too slow... Unless someone could tell how to speed up triggers. Regards, Jeff Marcos This e-mail is for the use of the intended recipient(s) only. If you have received in error, please notify the sender immediately and delete it. If you are not the intended recipient, you must not use, disclose or distribute this e-mail without the author's prior permission. Corporate Express checks all outgoing mail and accepts no liability for any loss or damage caused by software viruses. ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
