While I like the optimisation, the SQL syntax seems pretty horrible.
Could it not be done without changing the syntax at all, except to
change slightly how one defines a column? Given something like
CREATE TABLE item_name (
item_id INT PRIMARY KEY,
item_name VARCHAR(255)
)
CREATE TABLE item_set (
item_set_id INT PRIMARY KEY,
item_id INT REFERENCES item_name (item_id)
ON UPDATE CASCADE ON DELETE CASCADE
)
it seems to me that it would be possible for the database to
transparently implement this using the optimisation described.
Given that, maybe one could just add another keyword to the REFERENCES
statement that would actually do the reference with a "pointer"?
cjs
--
Curt Sampson <[EMAIL PROTECTED]> +81 90 7737 2974 http://www.netbsd.org
Don't you know, in this new Dark Age, we're all light. --XTC
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
