In January 2020, we introduced new spatial data types that will be replacing our existing geolocation features. This week, we released an update for our .NET SDK that will allow you to work with those new data types.
Remote work, particularly for technology-based jobs, is the new normal as the world grapples with the novel coronavirus. This creates many new challenges for teams that are used to working together on-site. It’s more important than ever that your team’s technology be the solution, not the problem.
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.
In another Recipe article, we discussed how to load data from the Backendless mbaas server using paging. In fact, data paging is only one of the features available in the data loading API. In this post, we are going to show how to fetch data objects with sorting. The sorting option can be combined with…
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.
Loading data objects from the Backendless persistent storage is a fundamental operation a large majority of the online/mobile applications require. Backendless Data Retrieval API is simple, yet very powerful.
In other articles, we’ve discussed how to load object relations using the auto-load and the one-step approach. Both of these approaches return a complex hierarchy of data where the parent object includes child entities at the time when it is retrieved from the server.