Re: Joins with nulls

> Perhaps another approach:
>
> How do you design a database, such that it won't have a blank, if the
> person who has the raw data goes home half way through. The tupple is
> half filled, the data that is entered is valid, but the rest is gone
> forever. Depending on the operator, 10% to 40% of my current data
> falls into this category.

If the person goes home half way through the transaction, then the transaction never got committed.

(And that's true even if you have a language that expresses the entire transaction in a single statement. )

If the transaction never got committed, nobody else can see any part of that tuple. It can't be shared.

Try another example. Received on Tue Nov 26 2002 - 13:39:32 CET