Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Suppose each AssetGroup object must have at least 1 Asset object . How to enforce this constraint in :
a) traditional SQL
b) NHibernate
I can check the number of children Asset before delete operation , but perhaps there are more declarative ways to do it .
In case of creating AssetGroup, does it force me to create an Asset first before creating an AssetGroup ?
You’re trying to deal with that at the wrong level.
This is a business-level constraint, not a data-level one. Do the validation in your business layer and you’ll be fine.
By “business layer” I mean either the entities themselves, or whatever you have on top of the data (NH/Repository) layer.