HasOne relations

Overview

A hasOne relation sets up a one-to-one connection with another model, such that each instance of the declaring model “has one” instance of the other model. A hasOne relation is a degenerate case of a hasMany relation.

Defining a hasOne relation

Use apic loopback:relation to create a relation between two models. The tool will prompt you to enter the name of the model, the name of related model, and other required information. The tool will then modify the model definition JSON file (for example, common/models/customer.json) accordingly.

Use slc loopback:relation to create a relation between two models. The tool will prompt you to enter the name of the model, the name of related model, and other required information. The tool will then modify the model definition JSON file (for example, common/models/customer.json) accordingly.

For more information, see Relation generator.

For example, consider two models: supplier and account.

{
  "name": "supplier",
  "base": "PersistedModel",
  "idInjection": true,
  "properties": {
    "name": {
      "type": "string"
    }
  },
  "validations": [],
  "relations": {
    "supplier_acct": {
      "type": "hasOne",
      "model": "account",
      "foreignKey": "supplierId"
    }
  },
  "acls": [],
  "methods": []
}

A supplier has one account, where the foreign  key is on the declaring model: account.supplierId -> supplier.id.

{
  "name": "account",
  "base": "PersistedModel",
  "idInjection": true,
  "properties": {
    "id": {
      "type": "number",
      "required": true
    },
    "acctmgr": {
      "type": "string"
    },
    "supplierId": {
      "type": "number",
      "required": true
    }
  },
  "validations": [],
  "relations": {},
  "acls": [],
  "methods": []
}

Alternatively, you can define a “hasOne” relation in code, though in general this is not recommended:

Supplier.hasOne(Account, {foreignKey: 'supplierId', as: 'account'});

If the target model doesn’t have a foreign key property, LoopBack will add a property with the same name. The type of the property will be the same as the type of the target model’s id property. Please note the foreign key property is defined on the target model (for example, Account).

If you don’t specify them, then LoopBack derives the relation name and foreign key as follows:

• Relation name: Camel case of the model name, for example, for the “supplier” model the relation is “supplier”.
• Foreign key: The relation name appended with Id, for example, for relation name “supplier” the default foreign key is “supplierId”.

Methods added to the model

Once you define the hasOne relation, LoopBack automatically adds a method with the relation name to the declaring model class’s prototype. For example: supplier.prototype.account(...).

supplier.account(function(err, account) {
  ...
});

var supplier = supplier.account.build(data);

var account = new account({supplierId: supplier.id, ...});

supplier.account.create(data, function(err, account) {
  ...
});

account.create({supplierId: supplier.id, ...}, function(err, account) {
  ...
});

supplier.account.destroy(function(err) {
  ...
});

supplier.account.update({balance: 100}, function(err, account) {
  ...
});