Live data from Hacker News

Realm 1.0

realm.io

21–30 of 112 posts

Re: Realm 1.0

#21
post #11

Can someone elaborate how this differs from JPA/Hibernate style ORMs ? The examples look suspiciously similar. EDIT: So i easily believe that it's nicer than CoreData, and I see that there is lots of potential to reduce an ORMs complexity by assuming a single Writer (Process of App), but the core Problem seems to be exactly the same. - And the solution looks also very familiar. -> Proxy Objects, Bytecode manipulation…

Realm is not a relational database, but an Object database. This means that we totally avoid the impedance mismatch when you try to map Java references to tables. In Realm, relationships are first-class citizens. This is also one of the reasons that we can provide lazy-loading for everything. With ORM's the API might look the same on the surface, but you usually run into problems when trying to access foreign collect…

Thanks for your answer.

Re: Realm 1.0

#22

The "What is Realm?" paragraph begins with "Realm is not an ORM". Jesus Christ, that was the very first line.

Well thats the reason I asked to elaborate on how they are different.

Re: Realm 1.0

#23

Earlier quoted context omitted.

1. "Realm is not an ORM, and is not built on top of SQLite. Instead we’ve built a full database for mobile app developers, one that uses native objects that are dynamically mapped to a full, custom database engine (not just a key-value store)." => Why not use the terms "object database" or "OODBMS", then ? 2. "Realm supports Java, Objective-C, React Native, Swift and Xamarin." => "React Native" is not a language, why…

> 3. What about Python ? Is there any practical way to use Python for mobile apps? Realm is only targeting mobile platforms AFAIK.

Some people are active in this domain, see: https://www.python.org/community/sigs/current/mobile-sig/ and https://mail.python.org/pipermail/mobile-sig/

Two approaches that seem to work (or to be promising) are Kivy (https://kivy.org/) for cross-platform and PyBee / VOC (http://pybee.org/voc/) for Android.

Re: Realm 1.0

#25
post #17

Earlier quoted context omitted.

Realm is not a relational database, but an Object database. This means that we totally avoid the impedance mismatch when you try to map Java references to tables. In Realm, relationships are first-class citizens. This is also one of the reasons that we can provide lazy-loading for everything. With ORM's the API might look the same on the surface, but you usually run into problems when trying to access foreign collect…

Sorry my edit was after your answer. Yeah well, literally ORM has relational in it, but you probably know what I mean. So it behaves more like a graph store? - Can I query bottom up / through collections ? I'm really interested in the technical details and their implications.

Yes, thinking about the internal structure as a graph will give you the right ideas.

We don't have support for collecting objects bottom up yet, bu t it is tracked here: https://github.com/realm/realm-java/issues/2232

Realm Swift/Objective C has support for bi-directional references and we are adding that to Realm Java shortly as well: https://github.com/realm/realm-java/issues/607 ..That will also help when doing bottom-up queries.

If you want to know more about the internal details. There is some talks/articles here that might interest you:

- https://realm.io/news/threading-deep-dive/

- https://realm.io/news/jp-simard-realm-core-database-engine/

- https://www.youtube.com/watch?v=vGFInG96KH4

Re: Realm 1.0

#26

VP Product at Realm here. Thanks to everyone on HN for the support over the years! We came out of YC in Summer 11 and it’s been a fantastic ride growing over the past few years. Would love to hear y’alls thoughts on what we should add next. Is there any reason why you’d still use SQLite?

R-tree :)

Also: text index and a way to "unmigrate" a database on iOS would be cool when developers are working on different branches at once, so they can restore their data when they have a different migration version in some container

Re: Realm 1.0

#27

VP Product at Realm here. Thanks to everyone on HN for the support over the years! We came out of YC in Summer 11 and it’s been a fantastic ride growing over the past few years. Would love to hear y’alls thoughts on what we should add next. Is there any reason why you’d still use SQLite?

> Is there any reason why you’d still use SQLite?

Windows. Specifically, my current project is targeting Windows desktop (not WinRT/UWP) in addition to mobile platforms and Mac.

Re: Realm 1.0

#28

VP Product at Realm here. Thanks to everyone on HN for the support over the years! We came out of YC in Summer 11 and it’s been a fantastic ride growing over the past few years. Would love to hear y’alls thoughts on what we should add next. Is there any reason why you’d still use SQLite?

I've been trying Realm for Xamarin recently and I've got to say I'm pretty disappointed with it, compared to my previous experiences with EF. My complaints are as follows: - No enum support - No inheritance support - Many LINQ operations aren't implemented, no select, no aggregate, etc. I have to do a ToList or ToArray to use these operations. And that was just what came up in the first day of usage... Why would I us…

Xamarin has been highly requested, so we have tried to make it available as quickly as possible as a pre-1.0 version to get the proper input from developers like yourself as to what should be prioritized. Love to keep getting your feedback on github as well. Thanks!

Re: Realm 1.0

#29

VP Product at Realm here. Thanks to everyone on HN for the support over the years! We came out of YC in Summer 11 and it’s been a fantastic ride growing over the past few years. Would love to hear y’alls thoughts on what we should add next. Is there any reason why you’d still use SQLite?

Is unsigned integer support coming any time soon? Right now I'm using an integer and a computed property (Swift) to reinterpret the bit pattern as an unsigned value, which is... okay, I guess, as the field doesn't ever need to be queried. Filesize really matters in my case, so I don't want to go up an integer size.

It just seems like an odd limitation - it's all bits!

Post reply on HN