Re: What does this NULL mean?

mountain man wrote:
> "David Cressey" <dcressey_at_verizon.net> wrote in message
<snip>
> The time will eventually arrive when
> the model of the code and the model of the data will be taken
> under one theoretical umbrella.

Some strands within the s/w development profession have addressed this better than others over the years.

I'm also in the process-&-data-are-two-sides-of-the-same-coin camp. If you zoom out, you see that we are working with input, processing, storage, and output. Data models are obviously required for each of these areas and processing is the big picture. You can see the processing clearly with input, processing, and output, but it is also implied with storage -- it is intended for use so there is an interface for input so there can be processing and output. Decisions related to data affect process and vice versa -- they are necessarily interwoven into a whole.

Some db theorists, or worse yet, practitioners, seem to want to consider stores without doors or customers. Some people are interested in cars without drivers too so they can look at them and admire their design. So I can see how this happens, but it is not the type of practical approach one needs in the business world.

--dawn Received on Wed Dec 21 2005 - 17:51:00 CET