Data objects in Backendless may have related properties not only with other tables, but also with Geo Points. These relationships may be declared programmatically or using Backendless Console. In this post I review the process of declaring a Data-to-Geo relationship in a data table schema.
Once a relationship is declared, you can do the following:
Link/unlink/manage data objects with related geo points using console.
Use Backendless code generator to create client-side code which reflects the structure of the tables. Continue reading →
Previously I have reviewed multiple techniques for loading data objects from the persistent server-side storage. There is a list of all articles categorized by topic. In this post I am going to review the API for loading data objects using an SQL query. I already wrote once about SQL queries in Backendless and that post described how to test queries using console. I recommend reading that post before reviewing the samples below.
Data objects stored in Backendless may have related objects through one-to-one or one-to-many collections. When objects are retrieved on the client side, these relations are materialized as collections of data in object’s fields or properties. Consider the following data object: Continue reading →
Notice the class does not include any fields/properties for
updated fields. Nevertheless, the call to save the updated object knew that it is already stored in Backendless. This is possible as a result of a feature that lets you declare any field or property your app might need. Also, notice the class neither implements any special interfaces nor extends any base Backendless classes – a pure data object class.