|
| Iniciado por guest, 07,ene. 2018 13:35 - 5 respuestas |
| |
| | | |
|
| |
| Publicado el 07,enero 2018 - 13:35 |
I am confused and think it's another of those strange Helpfile anomalies.
https://doc.windev.com/en-US/… describes how to backup a database. However when I do this it tells me it is only available for a Server database.
So why does it say it is available for Android and iOS???? Surely these would never support server databases.
So if the above is nonsense is there any way to have Wx do a backup easily other than how I do it currently by creating a WinZip file.
Thx. |
| |
| |
| | | |
|
| | |
| |
| Publicado el 07,enero 2018 - 13:55 |
Hi John,
I do no think this is an anomaly...
Yes, this instruction is for HFSQL C/S, but you use it in your program, ie on the CLIENT side, and both android and ios support CONNECTING to HF C/S, and therefore can initiate a backup on the server.
No, as for the easiest way to do a backup, -MY- answer is NOT TO DO ANY BACKUP, do a replication instead 
I stopped worrying about backups in 2014, when I wrote my wxreplication open source. Since then, I have been putting it in ALL my projects, if even JUST so that there is an automatic, quasi real time, backup of all the data on another machine, and ideally on a machine that is in another physical location.
Best regards |
| |
| |
| | | |
|
| | |
| |
| Publicado el 07,enero 2018 - 14:28 |
Thanks Fabrice. The trouble is I cannot get it working on the Client side using the example (suitably changed). So I don't know what to do.
As for Replication - I agree this is what I do now. However my Clients tend to use their devices Offline all the time. They travel all the time and very rarely have a connection to the Server. When they get home they stop using the app so the automatic synchronization function I have built in does not have a chance to work.
So whilst Replication is the best answer, I do feel the need for a local backup. But it would be good if I could get HBackup working on the Client side. |
| |
| |
| | | |
|
| | |
| |
| Publicado el 07,enero 2018 - 14:32 |
Oh reading your answer again Fabrice I think I see what I am missing. HBackup backs up TO a Server. So they need to be Online for it to work. In other words in my scenario it still won't work.
This leads me to a more general issue I have been arguing for a long time ....
Mobile means "mobile" and as such a connection is not guaranteed. So why do so many people (not you Fabrice) tell me I have to use WebServices etc. to do things when connections are never guaranteed.
With all due respect I wish Mobile developers would recognize this and stop thinking that Mobile apps always have a connection.
No offence intended of course. |
| |
| |
| | | |
|
| | |
| |
| Publicado el 07,enero 2018 - 20:36 |
Hi John
no, what you are missing is that this function works ONLY against a C/S DB.. it can be run FROM a mobile, but only to backup a C/S file, NOT a local one.
As for the webservice, I am in fact telling you the same things, as my replication system DOES use a webservice for the communication layer.
So when somebody tells you that you need to use a webservice, it does NOT NECESSARILY means that you don't have local data, as that is a completely separate issue.
However, it's true that some people advise to not have local data and connect to the distant DB via a webservice. I agree with you here, and that is NOT a good mobile solution. It's slightly better than a direct connection to a distant DB, as you have more control over the connection errors, but it is suitable only for application working in a place where they have constant connection anyway, and that is definitely NOT the mobile world.
As for your synchronization problem, one way to solve it is to have that process run in a PERSISTANT secondary thread. That way, even when the users are STOPPING the app, the secondary thread continues to run and do the synchronization WHEN it has a connection.
Best regards |
| |
| |
| | | |
|
| | |
| |
| Publicado el 08,enero 2018 - 09:51 |
| Thx Fabrice. I agree but these people tell me that Mobile SHOULD use a Web Service. What is worrying they should know better. Enough said! |
| |
| |
| | | |
|
| | | | |
| | |
|