Queries
Programmatically interacting with records on RONIN is made possible through its unique query syntax, designed to allow for accessing data in the most “humane” way possible, as it closely mimics the English language.
To retrieve a list of blog posts from RONIN, for example, you could run the following:
await get.blogPosts();
If you’d like to retrieve only a specific blog post, you could do so like this:
await get.blogPost.with.slug('new-pricing');
As you can probably already tell, RONIN’s syntax is quite straightforward to use while still providing enough flexibility to scale gradually as more advanced assertions are desired.
Components of the Query Syntax
Below, you can find a list of all the different parts of the RONIN query syntax.
Query Types
Learn more about how to perform different actions with queries:
-
Creating Records (
create
) -
Retrieving Records (
get
) -
Modifying Records (
set
) -
Deleting Records (
drop
) -
Counting Records (
count
)
Query Targets
Learn more about how schema slugs can be used to address records.
Query Instructions
Learn more about how to access specific records and format the query response:
-
Asserting Fields (
with
) -
Paginating Records (
before
,after
,limitedTo
) -
Ordering Records (
orderedBy
) -
Resolving Related
Records
(including
) -
Excluding Fields (
excluding
)
Composability
As RONIN’s query syntax mimics a plain JavaScript or JSON object in its form, you may choose to expand or compress the individual levels of the object at any position of your choice.
For example, both of these queries perform exactly the same action:
await get.blogPosts.with.slug('new-pricing');
await get.blogPosts({
with: { slug: 'new-pricing' },
});
Any level that contains a period (.
) can instead be a nested object if you decide so. This allows you to structure the query in any way you like, to keep it as simple as possible and as human-readable as possible, even as complexity increases.
Dot-String Notation
Additional flexibility is provided as every key inside the object can contain dot notation as well.
This is especially useful when addressing nested fields (either of a relational record or the RONIN metadata) or when writing extremely sophisticated queries, as the syntax continues to remain readable and even easy to augment with comments.
For example, the query below retrieves all records of the schema “Blog Post” where the author is matched using a given username/handle, and the record is older than a given date:
await get.blogPosts({
with: {
author: { handle: { being: 'elaine' } },
ronin: { createdAt: { lessThan: new Date() } },
},
including: ['author'],
});
In order to simplify addressing nested fields, RONIN supports “dot notation”, which may be used on any level of the query:
await get.blogPosts({
'with.author.handle.being': 'elaine',
'with.ronin.createdAt.lessThan': new Date(),
including: ['author'],
});
Another example of placing the “dot notation” on a different level could be:
await get.blogPosts.with({
'author.handle': 'elaine',
'author.email': 'elaine@kojima-productions.com',
});
Similarily, if you’d like to provide comment augmentation for extremely sophisticated queries, you can easily do so like this:
await get.teams.with({
// Only retrieve teams of the current Space.
'space.handle.being': spaceHandle,
// Exclude the current team.
'handle.notBeing': teamHandle,
// Exclude children of the current team.
team: [{ 'handle.notBeing': teamHandle }, { being: null }],
});
“OR” Conditions
In certain cases, you might want to express an “OR” condition in RONIN’s query syntax, by requiring one of two (or more) possible sub-conditions to match.
Achieving this is only a matter of using Arrays, rather than Objects, for your queries.
You can think about RONIN’s query syntax in the following way:
-
Objects require every nested property within them to match.
-
Arrays require at least one nested item within them to match.
In the following example, we want to retrieve a record of the “Blog Post” schema for which the “author” field matches at least one of two possible values:
await get.blogPost.with.author(['acc_vais0g9rrk995tz0', 'acc_fa0k5kkw35fik9pu']);
The array syntax can currently be applied to any level inside the with
query instruction:
await get.accounts.with.handle(['leo', 'juri']);
await get.accounts.with.handle([{ endingWith: 'test' }, { startingWith: '1234' }]);
await get.accounts.with([{ handle: { being: 'today' } }, { name: { endingWith: 'lamprecht' } }]);
You can even use it on multiple different nesting levels at once:
await get.accounts.with([{ handle: { being: ['juri', 'leo'] } }, { name: { endingWith: 'lamprecht' } }]);