hasOne and belongsTo update/destroy methods on scope

Note the following semantics:
- destroy on a hasOne relation will nullify the foreignKey (see also: #234)
- destroy on a belongsTo relation will effectively destroy the related item completely

Is this what's expected? Or should we introduce a flag to configure this?