on delete RESTRICT rule question

Hi there,

I need to be able to determine the delete restriction
of a row before the actual delete is performed on the
database. I need this only because i don't want to
wait for the database to throw an exception if i can't
delete a row, because of references integrity
problems; that's depending on the answer to this
question : how much it would take to determine if a
row can be deleted or not? is it possible that the
database keeps some records about how many
dependencies a row has in other tables?, when the
database is asked to delete a row, it will iterate
over all relationed tables to determine the
references?

I was thinking of implementing a service in my
application, that keeps records (a count) of how many
dependencies a row has (in some other tables), to be
able to determine as fast as possible if it can be
deleted or not. 

I think, i'm more interested in how the RESTRICT on
delete rule is implemented, and if i can relay on it
without worring about performance problems when my
database will grow to be very large.

Is SAPDB keeping some records about dependencies or it
searches for them only when it's needed?

Thanks,
Regards


                
__________________________________ 
Do you Yahoo!? 
All your favorites on one personal page ? Try My Yahoo!
http://my.yahoo.com 

-- 
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/maxdb?unsub=gcdm-maxdb@xxxxxxxxxxx