.
Cheers,
Phil
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Woodward
Sent: Saturday, 11 June 2005 10:01 a.m.
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] [UV] Triggers, RAID and SQL 2005
No, you can't get past the write statement if you are ru
Hi,
I will be out of the office from June 13th through June 15th. I will
return on June 16. I will not have access to e-mail or voice mail. If
a you need an immediate response to your e-mail please e-mail
[EMAIL PROTECTED] or you can call Frank at extension 467.
Thanks and have a great day!
UV 10.1.
BobW
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:owner-u2-
> [EMAIL PROTECTED] On Behalf Of phil walker
> Sent: Friday, June 10, 2005 2:50 AM
> To: u2-users@listserver.u2ug.org
> Subject: RE: [U2] [UV] Triggers, RAID and SQL 2005
>
> I know that are good
Just to add fuel to the fire - UniData triggers have no such
constraints. In fact, using the debugger was how I discovered that our
(old) development team thought it would be a good idea to install
triggers on a large client site at the end of the day. The next morning
wasn't a good day in support
not ideal...
Phil
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Friday, 10 June 2005 8:16 p.m.
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] [UV] Triggers, RAID and SQL 2005
We use them. they're good, though slower t
We use them. they're good, though slower than i-type pseudo triggers, they
give more flexibility.
Triggers begin a transaction, which you aren't supposed to be able to step
through using a debugger.
Regards,
--
Stuart Boydell
[EMAIL PROTECTED] wrote on 10-06-2005 13.57.58:
> I have found what I
I have found what I believe to be a problem with implementing triggers
in UniVerse.
If I have a trigger on a file and a developer is trying to resolve a
problem in a program which happens to update/delete that file an issue
using 'RAID' the debugger ;-) When the developer steps over the
write
