[Bug 3796] [UPDUseCases] Clarify how application constraints raise dynamic errors

http://www.w3.org/Bugs/Public/show_bug.cgi?id=3796


Ronald Bourret <rpbourret@rpbourret.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |




--- Comment #1 from Ronald Bourret <rpbourret@rpbourret.com>  2009-05-20 22:05:13 ---
Thanks for the changes. Unfortunately, there are still some ambiguities. 
Please make the following changes:

1) In section 1.1.3, change:

   ... by the following table:

to
   ... by the following tables:

2) Change the last sentence of section 1.1.3 to:

   The underlying database system has the following referential 
integrity constraints:

   o A foreign key on the BIDS table requires that BIDS.USERID contains a value
that is found in USERS.USERID

   o A foreign key on the BIDS table requires that BIDS.ITEMNO contains a value
that is found in ITEMS.ITEMNO

3) In section 1.1.4.8, change the next-to-last sentence from:

   This update violates an application constraint.

to

   This update violates the previously mentioned referential integrity
constraint.

4) Please clarify error generation in section 1.1.4.9. For example, change:

   An auction application constraint imposes that a bid cannot be made at a
lower price than the highest bid made so far on that item.

to:

   A trigger in the underlying database ensures that a bid cannot be made at a
lower price than the highest bid made so far on that item.

And change:

   Like the previous one, this update violates an application constraint,
therefore its execution will raise a dynamic error...

to:

   This update causes the previously mentioned trigger to return an error.
Therefore, its execution will raise a dynamic error...

Thanks.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Wednesday, 20 May 2009 22:05:22 UTC