enforce no master without detail

I'm just wondering ...

what would be the most elegant way to enforce the rule "don't create a master without at least one detail"
having a master-table and a detail-table connected via 1:n relationship? The desired behaviour should be an error being raised when committing an insert on the master-table where no details exist (similarily deleting the details and leaving the master should raise an error).

thanks,
stephan Received on Wed Aug 05 2009 - 03:50:39 CDT