As soon as you have data in persistent storage, the question of searching would be one of the first to come up. Indeed, how can you query the backend for data? We considered multiple options and elected to use the most popular one – SQL.
Backendless can create tables when you store object hierarchies from a client application. Also, we described how to manually create data tables using Backendless Console.
One of the hidden gems packed with features is Backendless REST Console. It is a part of Backendless Console and is located in its own tab on the Data screen. The Console does exactly what it sounds like – lets you run REST requests against your data tables.
The REST Console is a part of the Backendless Console. It is a versatile interface that lets you perform a complete CRUD (Create, Retrieve, Update, Delete) set of operations on your data stored in Backendless using the REST interface.
In another post, we describe how to add columns/properties to a Backendless table/class using Backendless Console. The types of properties reviewed in that post were all primitive: string, numbers, dates or boolean values. In addition to these data types, Backendless also supports relationships between objects stored in its persistent storage.
Previously we showed how to declare relationships between tables. Once a relationship is in place, specific objects stored in the tables may be linked with each other.
Data objects in Backendless can be connected to related properties not only in other tables, but also with Geopoints. These relationships may be declared programmatically or using Backendless Console. In this post, we will review the process of declaring a Data-to-Geo relationship in a data table schema.
Backendless database provides a very simple, but powerful API for storing, searching, updating or deleting application objects. The “feature 1” post demonstrates how to save objects with relations in Backendless using the APIs.
As data objects are being saved or updated with the API requests some properties of the objects may not have a value assigned to them. It may be necessary that for those properties a default value is assigned. This is identical to how relational databases may have a default value for a column.