--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-talk+unsubscribe@googlegroups.com.
To post to this group, send email to fireba...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/eb964d24-8d0b-4373-84e7-7b1acedf273b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi Ruben,What's the goal here? If you're worried about collisions, then you should probably either be using push() to ensure unique entries and work in more of an event stream, or utilize transactions if they will be writing to the same path.Ideally, that would be a better solution than trying to manage connectivity--a complex process that Firebase does well without any oversight.☼, Kato
On Wed, Jan 11, 2017 at 6:15 PM, Ruben González Torres <rube...@gmail.com> wrote:
Hi:I am building a collaboration app with Firebase Database. Because it is a complex collaboration app I need to save in the firebase only when the user is online (to avoid any collision between different users). I am not using offline capabilities but I am having a problem with the basic write/read functions when the device is offline. Because Firebase is saving the changes in a local DB first, even if the device is offline my app is showing the local data. And if the app is restarted then it shows the server data. I want to show only the server data.Is it possible to don't save on the local DB and save directly on the server DB?How can I detect if the update was saved correctly on the server?BestRuben
--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@googlegroups.com.
To post to this group, send email to fireba...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/eb964d24-8d0b-4373-84e7-7b1acedf273b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To know when your data is committed to the Firebase Realtime Database server, you can use aPromise. Bothset()andupdate()can return aPromiseyou can use to know when the write is committed to the database.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-talk+unsubscribe@googlegroups.com.
To post to this group, send email to fireba...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/2451a8a5-df68-4a31-aecf-a5fb7734102b%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/2451a8a5-df68-4a31-aecf-a5fb7734102b%40googlegroups.com.