See also:
Page Contents
Overview
A query is a read operation on models that returns a set of data or results. You can query LoopBack models using a Node API and a REST API, using filters, as outlined in the following table. Filters specify criteria for the returned data set. The capabilities and options of the two APIs are the same–the only difference is the syntax used in HTTP requests versus Node function calls. In both cases, LoopBack models return JSON.
Query | Model API (Node) | REST API |
---|---|---|
Find all model instances using specified filters.
|
Where filter is a JSON object containing the query filters. See Filters below. |
See Model REST API - Find matching instances. See Filters below. |
Find first model instance using specified filters. |
Where filter is a JSON object containing the query filters. See Filters below. |
See Model REST API - Find first instance. See Filters below. |
Find instance by ID. |
Where optional filter is a JSON object containing the query filters. See Filters below. |
|
Important:
A REST query must include the literal string “filter” in the URL query string. The Node API call does not include the literal string “filter” in the JSON.
LoopBack API Explorer adds “filter” to the query string, but you must enter Stringified JSON in the filter field. Also make sure that the quotes you use are proper straight quotes ( “ ), not curved or typographic quotation marks ( “ or ” ). These can often be hard to distinguish visually.
Tip:
If you are trying query filters with curl, use the -g
or --globoff
option to use brackets [
and ]
in request URLs.
LoopBack supports the following kinds of filters:
See Filters below for more information.
Examples
See additional examples of each kind of filter in the individual articles on filters (for example Where filter).
An example of using the find()
method with both a where and a limit filter:
Account.find({where: {name: 'John'}, limit: 3}, function(err, accounts) { /* ... */ });
Equivalent using REST:
/accounts?filter[where][name]=John&filter[limit]=3
Filters
In both REST and Node API, you can use any number of filters to define a query.
LoopBack supports a specific filter syntax: it’s a lot like SQL, but designed specifically to serialize safely without injection and to be native to JavaScript.
Previously, only the PersistedModel.find()
method (and related methods) supported this syntax.
The following table describes LoopBack’s filter types:
Filter type | Type | Description |
---|---|---|
fields | Object, Array, or String |
Specify fields to include in or exclude from the response. See Fields filter. |
include | String, Object, or Array |
Include results from related models, for relations such as belongsTo and hasMany. See Include filter. |
limit | Number |
Limit the number of instances to return. See Limit filter. |
order | String |
Specify sort order: ascending or descending. See Order filter. |
skip (offset) | Number |
Skip the specified number of instances. See Skip filter. |
where | Object |
Specify search criteria; similar to a WHERE clause in SQL. See Where filter. |
REST syntax
Specify filters in the HTTP query string:
?filter_filterType_=_spec_&_filterType_=_spec_....
The number of filters that you can apply to a single request is limited only by the maximum URL length, which generally depends on the client used.
Important:
There is no equal sign after ?filter
in the query string; for example
http://localhost:3000/api/books?filter[where][id]=1
Note: See https://github.com/hapijs/qs for more details.
Node syntax
Specify filters as the first argument to find()
and findOne()
:
{ filterType: spec, filterType: spec, ... }
There is no theoretical limit on the number of filters you can apply.
Where:
- filterType is the filter: where, include, order, limit, skip, or fields.
- spec is the specification of the filter: for example for a where filter, this is a logical condition that the results must match. For an include filter it specifies the related fields to include.
Using “stringified” JSON in REST queries
Instead of the standard REST syntax described above, you can also use “stringified JSON” in REST queries. To do this, simply use the JSON specified for the Node syntax, as follows:
?filter={ Stringified-JSON }
where Stringified-JSON is the stringified JSON from Node syntax. However, in the JSON all text keys/strings must be enclosed in quotes (“).
Important:
When using stringified JSON, you must use an equal sign after ?filter
in the query string.
For example: http://localhost:3000/api/books?filter={%22where%22:{%22id%22:2}}
For example: GET /api/activities/findOne?filter={"where":{"id":1234}}
Filtering arrays of objects
The loopback-filters module implements LoopBack’s filter syntax.
Using this module, you can filter arrays of objects using the same filter syntax supported by MyModel.find(filter)
.
Note:
We plan to convert all modules to use loopback-filter
, so it will become LoopBack’s common “built-in” filtering mechanism.
Here is a basic example using the new module.
var data = [{n: 1}, {n: 2}, {n: 3, id: 123}];
var filter = {where: {n: {gt: 1}}, skip: 1, fields: ['n']};
var filtered = require('loopback-filters')(data, filter);
console.log(filtered); // => [{n: 3}]
For a bit more detail, say you are parsing a comma-separated value (CSV) file, and you need to output all values where the price column is between 10 and 100. To use the LoopBack filter syntax you would need to either create your own CSV connector or use the memory connector, both of which require some extra work not related to your actual goal.
Once you’ve parsed the CSV (with a module like node-csv
) you will have an array of objects like this, for example (but with, say, 10,000 unique items):
[
{price: 85, id: 79},
{price: 10, id: 380},
//...
]
To filter the rows you could use generic JavaScript like this:
data.filter(function(item) {
return item.price < 100 && item.price >= 10
});
This is pretty simple for filtering, but sorting, field selection, and more advanced operations become a bit tricky. On top of that, you are usually accepting the parameters as input.
For example:
var userInput = {min: 10, max: 100}
data.filter(function(item) {
return item.price < userInput.min && item.price >= userInput.max
});
You can rewrite this easily as a LoopBack filter:
filter(data, {where: {input: {gt: userInput.min, lt: userInput.max}}})
Or if you just adopt the filter object syntax as user input:
filter(data, userInput)
But loopback-filter
s supports more than just excluding and including.
It supports field selection (including / excluding fields), sorting, geo/distance sorting, limiting and skipping.
All in a declarative syntax that is easily created from user input.
As a LoopBack user this is a pretty powerful thing.
Typically, you will have learned how to write some complex queries using the find()
filter syntax; before you would need to figure out how to do the
same thing in JavaScript (perhaps using a library such as underscore). Now with the loopback-filters
module, in your client application you can re-use
the same exact filter object you were sending to the server to filter the database without having to interact with a LoopBack server at all.