Re: Joins with nulls

Bob Badour wrote:

> "Finarfin" <finarfin_at_sympatico.ca> wrote in message
> news:NV4E9.410$IQ5.26532_at_news20.bellglobal.com...
>> Bob Badour wrote:
>> >

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.

My frustration with your answers stems from your desire to apply a theory that doesn't lend itself to any practical solution with the tools I have to work with. Just show me the DDL for the (Date, Time, Froth Depth at the Date/Time) example, given that the Date can be entered by default, but the other two require operator input and the operator may or may not physically enter one or both of them, whether he knows them or not. Once any of them have been entered, the data cannot be discarded.

JE Received on Tue Nov 26 2002 - 06:43:15 CET