What changed
Because the new agent is designed to work with multiple databases, the return value of the segment handler is no longer a Sequelize/Mongoose condition. Instead, you build a condition tree that the agent translates to the appropriate database syntax.API cheatsheet (Node.js)
| Legacy agent | New agent |
|---|---|
where: | handler body (return value) |
sequelize.where(...) | condition tree { field, operator, value } |
Performance tip
Many queries map directly to Forest condition trees, giving much better performance than performing the query yourself and then building a naiveid IN (...) condition.
Example
- Before (Node.js)
- After (Node.js)
- Before (Ruby)
- After (Ruby)