comments on draft-presuhn-referent-00.txt

[Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>]

After reading <draft-presuhn-referent-00.txt>, I felt that the
document is very much focussed on table indexing and that there could
be some more text about pointer references which are not associated
with table indexes. I have seen discussions whether

(a) pointers from table A to table B should be enforced in the sense
    that you defer row deletions until the references are gone as
    well

(b) whether you should delete rows when requested to do so leaving
    dangling pointers around

(c) reject row deletions until there are not pointers anymore,
    assuming the application understand why you reject a delete
    requet

(d) require that row deletions cleanup any dangling pointers	

All these solutions have some pros and cons and it would be nice if
the document could expand on this.

Do I have concrete text offer? No, at least not at this time. But
anyway, I thought that at least get theses variations listed somewhere
as open issues needed to be worked out would be a step forward.

/js

-- 
Juergen Schoenwaelder    <http://www.informatik.uni-osnabrueck.de/schoenw/>