HP3000-L Archives

February 1999, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"James Clark, Jr." <[log in to unmask]>
Reply To:
James Clark, Jr.
Date:
Tue, 16 Feb 1999 09:54:49 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (49 lines)
I can see where a warning would help in the development of code but not in
the production mode code. The transaction would need to be all commited or
all rolled-back not something in-between. So I would suggest an software
option to activate the warning for testing purposes and then when turned off
the app would receive an error thus rolling back the transaction.
My opinion about transactions is that it is easier to let the DB handle
undoing a transaction then having to code for it, but if I commit half way
through then get an error I then have to program for backing out the
commited entries and I am back where I started with having no transaction
monitoring.
Thanks for providing these great tools to accomplish our work. Keep up the
good work.

James

> -----Original Message-----
> From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
> Behalf Of B T Vikram Kumar
> Sent: Tuesday, February 16, 1999 6:17 AM
> To: [log in to unmask]
> Subject: Large Transaction in IMAGE
>
>
> Currently CSY Database lab is considering an enhancement to increase the
> transaction size for dynamic t ransactions (ie, transactions with a
> structure like DBXBEGIN - DBPUT/ DBDELETE/ DBUPDATE - DBXEND/ DBXUNDO).
> And also to give some sort of user control over the transaction. One
> feature, which is being planned to implement is that, to issue a warning
> to user when transaction size reaches a pre-defined soft limit. once
> this warning is issued, users can have two options. Option #1: User is
> forced to commit or rollback (DBXEND/ DBXUNDO). Option #2: Don't force
> anything, user may chose to rollback/ commit or ignore the message. If
> it is ignored, ultimately the transaction size may exceed the maximum
> possible value and get a stalled transaction (i.e. compulsory rollback
> and process abort). What we are seeking is your prefernce of the above
> two options, based on your valuable experince. Your feedback on this
> will help the lab in deciding on an implementation strategy and coming
> up with the solution.
>
> You may choose to post yor reply to 3000-L or mail privately to
> [log in to unmask]
>
> Thanks in advance
>
> Regards,
> Vikram
> CSY Database Lab
>

ATOM RSS1 RSS2