Radek Pietruszewski

sorry, but it's a no from me. This was considered and rejected, oh, like 4 years ago. `Posts.foo()` is _nice_, but it's not _clean_. I refuse to promote a coding...

> On the other hand, the modelRoot doesn't quite solve our issue as we wanna use the database in sagas and etc. Sorry, I'm not sure what that means, can...

> what if we do such replacements on Collection I don't immediately hate the idea - it seems logical that if a Model can be extended with methods for a...

I know it's WIP, but a few things will be required: - a Changelog entry - describe the feature briefly in the appropriate document in `docs-master/` so that others can...

amazing @pranjal-jain! Thanks for doing this work! I will try to check out the PR in the next week or so

Your insert query is very unsafe - please read up on SQL Injection. As for performance, try this: https://github.com/Nozbe/WatermelonDB/blob/master/src/Collection/index.js#L113 -- admittedly, it won't perform as well as a highly optimized...

> Do you have an example on how that prepareCreateFromDirtyRaw works? https://github.com/Nozbe/WatermelonDB/search?q=prepareCreateFromDirtyRaw > I quess you still have to call it for every entry? yes, but with a POJO, not...

@victorbutler Hey! Would you mind taking a few minutes to add to docs (https://github.com/Nozbe/WatermelonDB/tree/master/docs-master ), in the appropriate place, a short & sweet "troubleshooting" about this - explaining that if...

Make your backend faster. In nozbe.com I have an account that has on the order of 200 000 records, and calculating changes since last sync on a simple cloud virtual...

@KennanChan Good idea. I'm OK with having `.save()` as a method on adapter. I encourage you to submit a pull request with such an improvement