As we create DBLX on different mobile platforms, it becomes clear that we need some type of server table replication.
This can be used for a number of purposes, including the actual replication of the database server state to a second, backup db server.
If this is done correctly, we can also use the feature to replicate a server database to a mobile device. Once the mobile device has the database(s) it can use them for an application and not need to keep a connection to a remote DB server.
We will also need to add the ability to configure a set of tables as an 'application'. By having a way to find sets of tables that are related to an application, we can have the replication process copy down all the tables in a given set. This would allow mobile apps to call a DBLX server and ask for all the tables for an application.
The team will attempt to get this feature set into DBLX 1.5. More details will follow.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As we create DBLX on different mobile platforms, it becomes clear that we need some type of server table replication.
This can be used for a number of purposes, including the actual replication of the database server state to a second, backup db server.
If this is done correctly, we can also use the feature to replicate a server database to a mobile device. Once the mobile device has the database(s) it can use them for an application and not need to keep a connection to a remote DB server.
We will also need to add the ability to configure a set of tables as an 'application'. By having a way to find sets of tables that are related to an application, we can have the replication process copy down all the tables in a given set. This would allow mobile apps to call a DBLX server and ask for all the tables for an application.
The team will attempt to get this feature set into DBLX 1.5. More details will follow.