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.

Another post covered how to retrieve data objects from Backendless. The code in that article loads a collection of the Restaurant objects and although it does not show it, the related collection of the Location objects arrives un-initialized. That is the default behavior of Backendless Database when it comes to loading related objects. The code…

When working with Backendless, data you accumulate can easily be exported. The inner workings of the export process itself are quite complicated since it takes into account all the relationships within your data. For you, the user, this process is in fact quite simple.

In another post, we describe how data tables in Backendless map to the client-side classes whose instances contain persisted data objects. However, there are scenarios when the default mapping is undesirable. In that case, Backendless client libraries provide an API to override the mapping.

In another article, we wrote how to load the first object from a data table using API. For the purpose of symmetry (and out of common sense), there is also an API to load the last object from a data table in your Backendless Database. The last object is determined by the time when it is…

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.

Whether you develop with IntelliJ IDEA, Eclipse, or Android Studio, the Backendless library (jar) for Java/Android must be referenced as a dependency. The library includes all the APIs that provide access to the backend functionality. The library is deployed to the centralized Maven repository, which makes it easy to import it to any Backendless-powered app.

Geolocation is one of the most powerful features of Backendless. The geolocation service provides APIs for storing, searching and managing geolocation data. There are three main elements that the geolocation service operates on: geocategories, geopoints, and points metadata.