Jason Dobry
Jason Dobry
This would be solved by fixing #22 right?
In 3.x this has been fixed for `updateAll` and `updateMany`. I'm not sure why it wasn't fixed for `update`.
js-data-firebase works best when the key is part of the result set. If you use js-data-firebase to create records in firebase, then it will save the key to the result...
Yeah, right now the Firebase adapter is great for use cases where you have a small amount of data, such as app settings, user profiles, etc. Not great for data...
I only ever imagined `parent: true` to be something the http adapter uses.
> Firebase doesn't recommend to do a nested data structure I agree with that, as your Firebase database is just a large JSON tree, nested data requires that the client...
I think the plan here is for js-data-firebase 3.x to add a `FireStore` component that would extend the `DataStore` component found in JSData 3.x.
Thanks. I'll look at it eventually. I've been furiously debugging a memory leak that I can't pin down... On Mon, Apr 14, 2014 at 1:47 PM, Royce Holmes [email protected]: >...
My first instinct tells me no. I haven't committed any code changes since 2013, so I honestly don't remember. I don't work on this repo anymore, and I don't plan...
RethinkDB has a single master architecture (and immediate consistency), though read queries are automatically parallelized across shards/replicas.