Re: A question for Mr. Celko
Date: Tue, 20 Jul 2004 05:32:03 GMT
Message-ID: <n72Lc.7919$mL5.70_at_newsread1.news.pas.earthlink.net>
John Jacob wrote:
>>EXACTLY! This means that I can use characteristic functions on >>columns, [...]
>
>
> The only definition I can find for characteristic function is a fancy
> word for the in operator. Is this the meaning you are intending? [...]
I don't know what John means. However, Rozhenstein developed some interesting SQL based on Sybase and what he called characteristic functions - functions which return 1 when a condition is true and 0 otherwise. You can Google on:
rozhenstein + characteristic + function
The first links lead to:
http://www.edbarlow.com/macros/macro_1.htm
There's also a reference to the out of print book on Amazon. I have a disintegrating copy on a bookshelf somewhere, and some worked examples for Informix databases on disk. I could make some of those available if there was interest enough.
> As for no recursion, self-references, and indeterminable sets, it
> sounds to me like this is just unnecessarily restricting the power of
> the language, a technique extremely common in today's systems, and one
> of the reasons relational languages get such a bad rap. Can you give a
> specific case where allowing relation-valued attributes would result
> in a wrong answer? Are you suggesting that allowing list, tuple, and
> relation-valued attributes somehow makes the language inconsistent
> (inconsistent in the formal sense meaning it would be possible to
> derive contradictory theorems)?
-- Jonathan Leffler #include <disclaimer.h> Email: jleffler_at_earthlink.net, jleffler_at_us.ibm.com Guardian of DBD::Informix v2003.04 -- http://dbi.perl.org/Received on Tue Jul 20 2004 - 07:32:03 CEST