realm-java UNIQUE

How to determine the class that the field name unique? Just as Primary keys?

Mar 16 '15 07:03 crysan

Yes, so far that's the only way, but we're considering to support some kind of annotation for field value uniqueness

Mar 17 '15 11:03 emanuelez

Just to be curious. Do you have a use case for this that isn't already covered by using @PrimaryKey?

Mar 17 '15 16:03 cmelchior

The problem was solved. Only after the introduction of a unique field in the table, we had to alter the program logic. There were: realm.beginTransaction(); Authors author = realm.createObject(Authors.class); author.setUrl_base("pptr"); realm.commitTransaction(); Now: Authors author = new Authors(); author.setUrl_base("pptr"); realm.beginTransaction(); realm.copyToRealmOrUpdate(author); realm.commitTransaction(); Very unfortunate that because of one field had to rewrite the code.

Mar 18 '15 00:03 crysan

That happens because you don't set your unique field. If you did you would not have to use standalone objects

Mar 18 '15 11:03 emanuelez

Ok.

Mar 19 '15 00:03 crysan

@emanuelez sorry I'm confused, would you mind giving a little code snippet of what you are talking about?

Mar 19 '15 01:03 mclark4386

But I cited above code that used prior to the introduction to the table a unique field, and after it. Now you have to write one line of code to add more new rows to a table.

Mar 19 '15 01:03 crysan

SQLite also has different modes for conflict resolution when it comes to uniqueness constraints we can consider: https://www.sqlite.org/lang_conflict.html

Aug 12 '15 10:08 cmelchior

:+1: waiting for this enhancement :)

Aug 13 '15 17:08 tarigancana

@beeender @cmelchior Is this feature coming anytime soon?

Feb 16 '16 00:02 AlokBansal8

Realm is lacking important feature. realm even has no compound key. so we have to calculate compound key manually.so in practical development, realm is useless. Realm has no roadmap.so don't expect anything.

Feb 16 '16 23:02 wyvern610

@cmelchior now that Primary Keys also imply that the value cannot be changed once persisted, is there a chance for a @Unique constraint which doesn't force you into the "value cannot be changed once persisted" limitation?

Sep 23 '16 08:09 Zhuinden

+1

Sep 29 '16 13:09 mfissehaye

+1

Nov 14 '16 08:11 2mwrzesinsky

+1

Nov 22 '16 17:11 the-dr-lazy

+1

Jan 03 '17 13:01 YaroslavYrm

Any news on this, I'm still waiting for this feature

Mar 15 '17 12:03 lednhatkhanh

+1

Apr 04 '17 16:04 shobhitpuri

I want to make field 'itemName' of Table Item to be unique in Android Realm. It means 'itemName' should not contain duplicate values. Is there any other way to achieve this except Primary key.. Thanks..