URL domain (too much SODA)

In article <3AF336A0.6098_at_ix.netcom.com>, Lee Fesperman says...
>
>Per Schröder wrote:
>>
>>
>> If you consider Chris Date or Hugh Darwen to be powers within the
>> relational world, you will find that they oppose the "class=relation" view.
>> They propose "class=domain".
>>
>> Read the book "Foundation for Future Database Systems: The Third Manifesto"
>> by C Date and H Darwen.
>>
>> Or read an interview with Date:
>> http://www.dbmsmag.com/int9410.html
>
>Also see Date's Debunkings article - "Chris Date Comments on URLs, Objects, and
>Relational Technology" (http://www.firstsql.com/dbdebunk/url1.htm).

So you claim that you can store any java objects, for example, URL in the column, right? Would you also be able to index by something like url.openConnection().getLastModified()? (I need to query URLs that has been changed their content lately and want it quick). A related question is, if you execute java methods on server side?

One of the issues related to URL in the database is that if I take C.Date's position not to store references in the database literally, then I probably don't want to store URL's -- aren't URLs references after all? Received on Sat Jul 21 2001 - 20:02:00 CEST