-Original Message-
From: [EMAIL PROTECTED] on behalf of steven mcphelan
Sent: Tue 4/5/2005 3:57 PM
To: hardhats-members@lists.sourceforge.net
Cc:
Subject:Re: [Hardhats-members] Maintaining database integrity
[KSB] <...snip...>
Is GT.M fully compliant with the
-Original Message-
From: K.S. Bhaskar [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 05, 2005 7:06 PM
To: Steve McPhelan
Subject: Re: [Hardhats-members] Maintaining database integrity
Steve --
I cannot reply to the hardhats list from my Blackberry (from which I am
replying to your
ED]>
To:
Sent: Tuesday, April 05, 2005 12:29 PM
Subject: Re: [Hardhats-members] Maintaining database integrity
> I know that I need to understand this entire process,
> which I currently don't. But I learn best by finding
> answers for specific questions.
>
> So in this sit
r not once the
> > > disk filled up. The only way I knew this
> happened
> > > was that the system
> > > eventually crashed when disk had gotten so
> corrupted
> > > with these random
> > > writes to any block.
> > >
> > > Do you r
> trapping a particular type of error? Suppose that
> the parent does not want the child trapping (and
> perhaps ignoring or mishandling) a error?
> M does not provide that and I don't know if any of
> the languages you sited does either.
>
>
> - Original Messag
ght about
namespacing errors and restricting applications to trapping errors in
their namespace, but I don't think the standard allows this.
>
> - Original Message -
> From: "Kevin Toppenberg" <[EMAIL PROTECTED]>
> To:
> Sent: Tuesday, April 05, 2005 9:
ir own user defined error trap? I
> > think not. I can see
> > one exception to this, possibly. You set the error
> > trap and look for a
> > specific error message. All other messages are
> > treated as fatal and sent to
> > the Kernel. Prior to the %ZISH utilitie
f any of the
languages you sited does either.
- Original Message -
From: "Kevin Toppenberg" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, April 05, 2005 9:31 AM
Subject: Re: [Hardhats-members] Maintaining database integrity
> In the languages that I am familiar with, such
e at the end of
> a file was to examine
> $ZE["ENDOFILE". This example is not valid now since
> we have the %ZISH
> utilities.
>
> - Original Message -
> From: "Greg Woodhouse" <[EMAIL PROTECTED]>
> To:
> Sent: Monday, April 04, 200
om: "Greg Woodhouse" <[EMAIL PROTECTED]>
To:
Sent: Monday, April 04, 2005 6:48 PM
Subject: Re: [Hardhats-members] Maintaining database integrity
--- steven mcphelan <[EMAIL PROTECTED]> wrote:
There is no way in Hades I would support this unless it was done
properly.
Are you
nly way to tell you were at the end of a file was to examine
$ZE["ENDOFILE". This example is not valid now since we have the %ZISH
utilities.
- Original Message -
From: "Greg Woodhouse" <[EMAIL PROTECTED]>
To:
Sent: Monday, April 04, 2005 6:48 PM
Subject: Re: [Ha
You can do dumb things with try blocks in Java, too, but just as you
generally have several catch clauses for different classes of
excceptions, the only reasonable thing to do is check the value of
$ECODE and act accordingly. At some point, I think you have to be
willing to put the burden on the p
--- steven mcphelan <[EMAIL PROTECTED]> wrote:
> There is no way in Hades I would support this unless it was done
> properly.
Are you suggesting that I'm saying it should be done improperly?
Two techniques that I believe could be used to advantage are sertting
$ECODE for user defined errors (of
is treat all
> errors as fatal, log them
> to the error trap, and disconnect that user?
>
> If every VA VistA programmer was a George Timson or
> a Michael Distaso then I
> would have such reservations.
>
>
> - Original Message -
> From: "Gregory Woodhouse&quo
Distaso then I
would have such reservations.
- Original Message -
From: "Gregory Woodhouse" <[EMAIL PROTECTED]>
To:
Sent: Monday, April 04, 2005 12:54 AM
Subject: [Hardhats-members] Maintaining database integrity
> I've noticed there's been a lot of discus
4/2005 12:54 AM
To: hardhats-members@lists.sourceforge.net
Cc:
Subject: [Hardhats-members] Maintaining database integrity
I've noticed there's been a lot of discussion of dangling pointers and
other types of database integrity issues at the application level. My
exper
I've noticed there's been a lot of discussion of dangling pointers and
other types of database integrity issues at the application level. My
experience has been that these sorts of problems are much more common
than problems at the global level (i.e., in the MUMPS subsystem).
Part of the proble
17 matches
Mail list logo
