Re:WatermelonDB, a database for React and React Native apps
by jonnydubowsky on Tuesday September 11, 2018 @02:10PM
(#17961996)
Thanks for this concise example! This helped me to understand why I should try it out, and led me to demoing this myself. I'll report back my findings
Re:WatermelonDB, a database for React and React Native apps
by nepeckman on Tuesday September 11, 2018 @11:17AM
(#17960496)
So is it fair to say its a React specific ORM, that automatically makes the mapped objects observable (an OORM, if you will)? Just trying to understand the level of abstraction that you're going for.
Re:WatermelonDB, a database for React and React Native apps
by radex on Tuesday September 11, 2018 @11:35AM
(#17960655)
That's a fair description, yeah!
Re:WatermelonDB, a database for React and React Native apps
by amelius on Tuesday September 11, 2018 @01:58PM
(#17961908)
Does that mean that if user A makes an update to the database, then user B (on a different computer) will see the update?
For example, if you have a todo app, and you mark a task as done, you'd want the task component to re-render, the list to re-render (put the task at the bottom), and update the right counters (the counter of all tasks, and a counter of all tasks in ta project), etc. I hope you're getting the point.
Watermelon is an observable abstraction on top of SQLite (or an arbitrary database), so that you can connect data to components and have them update automatically