So data is persisted totally independently of the SQLite engine? Straight in the file system?
Show HN: Realm for Android
61–66 of 66 posts
Re: Show HN: Realm for Android
#62Honestly, SQLite has a lot of utilities, tutorials, useful adapters and UI hooks in Android. Core Data similarly on iOS. If you want me to go to your framework instead, you'd have to provide something better than just redoing the API. E.g. network sync like Couch does.
I have just had a look at realm doc, but compared to core data, it seems to provide a MUCH cleaner api, especially regarding threading and transaction ( which i think i'm only starting to get right after having coded with core data for two years).
I do agree that net syncing would definitely be a killer feature for me as well, but it's probably not the case for the average project ( which probably uses custom web services for crud on the serve side).
Re: Show HN: Realm for Android
#63Given the insert speeds, I'm guessing they're (still) not reusing compiled statements. I mentioned this last time I saw Realm on the front page[1], but their benchmarks are misleading without at least mentioning that they're doing this. I'm still very much interested in Realm, and LOVE having a competitor to SQLite. But don't mislead your customers. [1]: https://news.ycombinator.com/item?id=8043332 where seepel finds…
That was a totally 100% fair point you made when we launched for iOS, and something we had completely overlooked. Your comment immediately prompted us to update our bench code to reuse compiled statements and, we’ve been using updated charts to document our iOS performance since then (e.g.: https://speakerdeck.com/timanglade/realm-overview-at-the-sil... ). See other comment ( https://news.ycombinator.com/item?id=8390…
Cool, thanks! I've mostly been looking at the iOS announcement page, which hasn't changed - harder to track down other materials you've used for promotion :/ Not that an old blog post is a great barometer of such things, of course.
Thanks again for looking into it and updating the material - far too many groups just gloss over (glaring) problems with their micro benchmarks, and it just sours all their future claims. Glad you're not one of them :)
Re: Show HN: Realm for Android
#64So data is persisted totally independently of the SQLite engine? Straight in the file system?
Absolutely - it's a totally new C++ fast nosql fully ACID database underneath. The database has been in development for the past 3 years, so it's not just a quick hack :-)
Re: Show HN: Realm for Android
#65Your JavaDocs miss a rather important information that Java SDK needs to be switched from 1.6 to at least 1.7 (in Android Studio, under Project Settings) for the thing to work! Otherwise it can't be run:
Error:Exception thrown while constructing Processor object: io/realm/processor/RealmProcessor : Unsupported major.minor version 51.0
Re: Show HN: Realm for Android
#66Earlier quoted context omitted.
I use Parceler ( https://github.com/johncarl81/parceler ) with gson. So gson for network data, then parceler for passing parcels around between activities/fragments.
Doesn't this require annotating the class? What if I can't change the class implementation?
One way to use Parceler is to annotate the class. There are a lot of other options though, including configuring the class outside of the class using @ParcelClass (useful for libraries) or writing a ParcelConverter.