Realm-java: RealmList<Integer / String / ...>
Dear realm-Team,
I'm really impressed by Realm and I do like the way you're providing support and solutions on github, SO and gGroups! I like working with Realm - however there are three really big drawbacks for me:
1) No model-instantiation by = new ... - I know you're on it. I can't wait for this! Do we have to wait for the "whole" JSON-Upgrade or will there be an earlier release providing this feature?
2) No model-passing across threads. That's hindering all the great benefits of EventBus and Android Priority Job Queue. But I read that it will be possible in the further versions and I'm looking forward on this.
3) The reason for this issue:
In my model class I'm allowed to have primitive fields as well as object fields of objects that extend RealmObject.
But I'm not allowed to have a field type like RealmList<Integer> or RealmList<String>.
However it is possible to work around this by
RealmList<RealmString> names;
and
public class RealmString extends RealmObject {
private String name;
// getter & setter
It works but it's _really_ ugly and should be unnecessary in my opinion.
Is there any improvement planned regarding this?
Thanks again for your great work - I'm glad Realm helps me developing my app!
Related PRs:
- [ ] API design (#4165)
- [ ] Implementation (#5031)
an-k
All 139 comments
I had bit of worries about the Realm design but after using it a lot i have seen it is done just right. My primary use of Realm is to pass data between threads (background processing and UI) and it works perfectly. It is so fast that even AsyncTasks are not needed anymore. Great work. Just few bugs left but easy to work around while waiting for the completion. I hope the next release comes out soon.
codezion
on 18 Nov 2014
@an-k I think that your suggestion (RealmList<String> etc.) is a good one. The complexity of implementing it is "less than impossible" but "greater than trivial". In particular the querying these lists of primitive types could be a bit tricky.
To make a long story short, I can give you a time frame in which it will be implemented.
kneth
on 18 Nov 2014
@kneth Thanks for your reply! You can give a time frame? That's great, so when will that probably be?
an-k
on 18 Nov 2014
@an-k Sorry for being unclear (I forgot a "not"); we don't have any time frame as we haven't decided if we wish to support it.
kneth
on 19 Nov 2014
@kneth This issue is the major reason for not using it in production yet, I can't change my JSON input, so to use it, I would have to do some really ugly tricks.
And with issues #489 and now #682 rising, I think it should be considered worth supporting.
For my use cases, if it got serialized as a string in the database and back as List, without any type of in db querying (no need to limit, search, just retrieve all), would be perfect.
I think that should be added some kind of RealmPrimitive class or an @ElementCollection annotation like the JPA 2 has.
Hazer
on 24 Dec 2014
Can I ask what the current state and/or priority of this feature request is?
Or: What is the recommended workaround for now?
jenzz
on 7 Feb 2015
I agree that this is a worthwhile feature. +1.
mpost
on 8 Feb 2015
Yes, please
ghost
on 11 Feb 2015
+1
kboyarshinov
on 12 Feb 2015
Would help solve issues like http://stackoverflow.com/questions/28733024/gson-deserialization-of-liststring-into-realmlistrealmstring
+1
kaushikmukunda
on 26 Feb 2015
+1
Not only primitive datatypes should be mentioned. Enums should be set in a list too.
FHellmann
on 7 Mar 2015
+1 for the List of primitive and also +1 for the Enums.
I'm actually kinda stuck now as I have a JSON with a list of strings that needs to go to the DB, not quite sure yet how to deal with that.
theyann
on 18 Mar 2015
+1
RobertoArtiles
on 30 Mar 2015
+1
kbpontius
on 17 Apr 2015
+1
jmachete
on 25 Apr 2015
+1
marianmoldovan
on 27 Apr 2015
+1
theostanton
on 30 Apr 2015
+1
eygraber
on 1 May 2015
A list of Strings is a very common use case for JSON responses. When you are given an array of Strings such as
"phoneNumbers":["000-000-0000", "111-111-1111"]
and you need to store it in the database, you need a list of Strings.
Implementing a workaround for every instance of a JSONArray of Strings would be bloated and ugly, unless I'm not understanding the workaround correctly. Can I create a RealmString once and use it in place of String everywhere that I would need a RealmList of Strings? How would I get RetroFit (REST library from Square) to play nice with such an implementation?
In any case, having this issue resolved would simplify the code and it seems that many people are looking for the same feature. Perhaps the priority of this feature should be increased over something else.
harish1312
on 12 May 2015
@harish1312 In the documentation (http://realm.io/docs/java/latest/#other-libraries) you can read on how to use Realm with RetroFit and GSON.
kneth
on 13 May 2015
+1
thecodingwizard
on 3 Jun 2015
+1
yoavst
on 12 Jun 2015
+1
LouisCAD
on 25 Jun 2015
+1
dulakm
on 11 Jul 2015
+1
azizj1
on 23 Jul 2015
+1
pavanjaju
on 11 Aug 2015
+1
jmodrako
on 13 Aug 2015
+1
jk2K
on 17 Aug 2015
+1
ganlaw
on 24 Aug 2015
+1
skptl
on 1 Sep 2015
+1
tehwayne
on 1 Sep 2015
+1
subhasha1
on 3 Sep 2015
+1
natanloterio
on 3 Sep 2015
+1 This is a very important one.
mmvicsonvictor
on 15 Sep 2015
+1
rajyvan
on 26 Sep 2015
+1
jaivikram
on 15 Oct 2015
+1
davroux
on 22 Oct 2015
+1
oiramcro
on 25 Oct 2015
+1 of course
HappyDr0id
on 17 Nov 2015
+1
gabuchan
on 19 Nov 2015
+1
AlexAlbala
on 25 Nov 2015
+1
gorje001
on 30 Nov 2015
+1
laurentiuonac
on 2 Dec 2015
+1
pandringa
on 8 Dec 2015
+1
claudioredi
on 10 Dec 2015
+1
riyase
on 10 Dec 2015
+1
tgbarker
on 15 Dec 2015
+1
skhaz
on 21 Dec 2015
+1
pratamawijaya
on 22 Dec 2015
+1
AamirAbro
on 23 Dec 2015
+1
nomisRev
on 29 Dec 2015
+1
sam33rdhakal
on 5 Jan 2016
+1
paulpv
on 9 Jan 2016
+1
celikin
on 11 Jan 2016
I'll +1 for notifications.
CDRussell
on 11 Jan 2016
+1
arshakavag92
on 11 Jan 2016
+1
dlet24
on 15 Jan 2016
+1
hendry64
on 18 Jan 2016
For any Kotlin users out there who don't want to manage a large tree of connected objects, I've been using this.
https://gist.github.com/bclymer/f569fffb41bab046c2d1
It creates a single RealmObject by storing the Ints or Longs as a comma delimited String. Then it uses an extension function to recreate the List<Type>
bclymer
on 21 Jan 2016
+1
MGaetan89
on 23 Jan 2016
+1
erakitin
on 25 Jan 2016
+1
pavel-mukhanov
on 25 Jan 2016
+1
lman
on 25 Jan 2016
In #1652, a workaround was provided until it is supported in realm.
I don't think it was given here, so here it is: https://gist.github.com/cmelchior/1a97377df0c49cd4fca9
MGaetan89
on 26 Jan 2016
+1 like everyone
Thx ;-)
SilkSama
on 4 Feb 2016
+1
pauloavelar
on 5 Feb 2016
+1
ruclip
on 8 Feb 2016
+1
kim-montano
on 9 Feb 2016
+1
xdgimf
on 9 Feb 2016
+1
saityoukou
on 10 Feb 2016
Why isn't this supported until now? Definitely +1
mehrad-rafigh
on 10 Feb 2016
+1
Crysis21
on 16 Feb 2016
+1
relaxedSoul
on 18 Feb 2016
+1 for this essential feature.
radi-ratlh
on 23 Feb 2016
+1
pbodsk
on 24 Feb 2016
+1
shmidt
on 24 Feb 2016
A year and a quarter later this issue is still open and has ~75 votes.
Seems like kind of a high important issue.
paulpv
on 24 Feb 2016
+1
pedrox-hs
on 25 Feb 2016
+1
alhazmy13
on 1 Mar 2016
+1
wwwlight
on 2 Mar 2016
+1
everyun
on 4 Mar 2016
+1
silva96
on 5 Mar 2016
+1
Queatz
on 6 Mar 2016
+1
mithrann
on 10 Mar 2016
+1
ZherebtsovAlexandr
on 14 Mar 2016
+1
Waboodoo
on 17 Mar 2016
+1
batista-mihai
on 21 Mar 2016
+1
dbauduin
on 22 Mar 2016
+1
dhenry
on 23 Mar 2016
Will implements ? RealmList<RealmString> strings; retrofit recongnize as object. I Need String
marcelohd
on 23 Mar 2016
+1
sstoyanova
on 29 Mar 2016
++i
kimbeejay
on 29 Mar 2016
+1
ilyator
on 29 Mar 2016
+1
peter-boot
on 31 Mar 2016
+1
doubleDragon
on 31 Mar 2016
+1
jagtejsodhi
on 2 Apr 2016
+1
micronax
on 2 Apr 2016
+1
abohomol
on 2 Apr 2016
+1
chmoder
on 2 Apr 2016
+1
ramirorinaldi
on 5 Apr 2016
+1
Unlimity
on 5 Apr 2016
+1
drobyshys
on 5 Apr 2016
This is pretty much the only feature in Realm that's still missing for it to be easy to use for any use-case. I wonder what's up with it.
It's not waiting core anymore, so I wonder what's the hold-up on this one.
Zhuinden
on 6 Apr 2016
+1
Rakatan
on 7 Apr 2016
+1
alexaccandr
on 8 Apr 2016
@Zhuinden We are currently focusing on support, bugs and P1 issues. Don't worry, we haven't forgot the P2 issues, and we hope to work on them very soon.
kneth
on 8 Apr 2016
+1
neokree
on 9 Apr 2016
+1
Dima564
on 12 Apr 2016
@kneth I'm just surprised this is not P1.
Zhuinden
on 12 Apr 2016
++
r-cohen
on 16 Apr 2016
+1
zzerk
on 16 Apr 2016
+1
RJFares
on 19 Apr 2016
+1
feludens
on 24 Apr 2016
+1
DaveInga
on 24 Apr 2016
+1
kosmonastya
on 26 Apr 2016
+1
droidizer
on 27 Apr 2016
+1
theisegeberg
on 28 Apr 2016
+1
DanMorganiOS
on 1 May 2016
+1 for the List of primitive
imp8468
on 4 May 2016
+1
wengelef
on 5 May 2016
+1
s4x
on 6 May 2016
+1
paulimfavarato
on 10 May 2016
+1
hari2109
on 10 May 2016
+1
nimitsolanki
on 10 May 2016
+1
dawidhyzy
on 10 May 2016
+1
ItsCalebJones
on 13 May 2016
+1
iguerendiain
on 13 May 2016
+1
jpmcglone
on 16 May 2016
+1
angcyo
on 16 May 2016
+1
sergiomarqmoura
on 17 May 2016
+1
andriipanasiuk
on 19 May 2016
+1
giaotuancse
on 23 May 2016
How is this still not supported?!?
b-raines
on 25 May 2016
+1
hasanabuzayed
on 2 Jun 2016
+1
henriquedesousa
on 2 Jun 2016
Can someone from the team lock this conversation until there is some news? For the moment it's just spamming everyone watching.
If someone else want to follow it, there is a "Subscribe" button on the right...
MGaetan89
on 2 Jun 2016
Everyone should really get used to using the nice new smileys in the top description field of the issue :-) But we will Lock this for now.
This feature is among a handfull of top features that we hope to take on next. We will however give the current 1.0 a bit of peace to ensure stability before we push a lot of new features.
bmunkholm
on 3 Jun 2016
See also http://stackoverflow.com/questions/39804941/what-the-best-way-to-use-liststring-in-realm-android
kneth
on 4 Oct 2016
Work in Realm Core can be tracked here: https://github.com/realm/realm-core/issues/1881
cmelchior
on 17 Jan 2017
Related issues
bfichter
路
80Comments
cornflakes
路
51Comments
cmelchior
路
100Comments
hohnamkung
路
141Comments
Zhuinden
路
73Comments