Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a232454eed0dcf73

Jump to content

// Workers AI · dad joke modeWhy was the exclusive relationship data lonely? It was locked in a bind.

From Wikipedia, the free encyclopedia

In computing, an exclusive relationship is a type of Relationship in computer data base design.

In Relational Database Design, in some cases the existence of one kind of relationship type precludes the existence of another. Entities within an entity type A may be related by a relationship type R to an entity in entity type B or entity type C but not both. The relationship types are said to be mutually exclusive. Usually, both relationship types will have the same name.

Example

[edit]

A Data (Entity A) could be Sent (Relationship Name) to a Monitor (Entity B) or a Printer (Entity C) to be shown. In this case, the relationship between the Monitor and Printer at one side and Data at the other side is an Exclusive Relationship. Of course it is assumed that Data could be sent to only one of the targets at a time, not to both.

     --- Sent_To ---> Monitor
 Data 
     --- Sent_To ---> Printer

References

[edit]
  • Jan L. Harrington, Relational Database Design Clearly Explained, Morgan Kaufmann, 2002, ISBN 1-55860-820-6, pages 354-355