Please enable JavaScript.

Coggle requires JavaScript to display documents.

Realm (Java (Realms (In-Memory Realm (using inMemory() in…

- - - - primary(boolean, byte, short, int, long ...)
      - Date and byte[]
      - supported to model relationships
        
        subclass of RealmObject and realmList<? extends RealmObject>
      - The boxed types (Boolean, Byte, Short, Integer, Long, Float, Double)
      - Null
        
        required annotation can be used to tell Realm to enforce checks to disallow null values (Boolean, Byte, Short, Interger ... byte[], and Date)
        
        Compiling will fail when files with other types have the Required annotation
        
        Primitive types and the RealmList required implicitly
        
        RealmObject type are allways nullable
      - Auto-Updating Objects
        
        Modifying objects that affect the query will be reflected in the results immediately
        
        To know when Realm data is updated indicating when your app's UI should be refreshed
      - Indexing properties
        
        Only support indexing: String. byte, short, int, long, boolean and Date fields
        
        Making inserts slower and the data file larger but queries will be faster
      - Ignoring properties
        
        Not add a field to disk
        
        static and volatile are ignored default
      - Primary keys
        
        Using annotation PrimaryKey
        
        The filed type has to be either string (String) or integer (byte, short, int, or long)+ boxed variants (Byte, Short, Integer, Long)
        
        Using a string filed as a primary key implies that the field is indexed(the annotation PrimaryKey implicitly sets the annotation Index)
        
        copyToRealmOrUpdate() it possible to use(If classes without primary keys , an exception will be thrown)
        
        When calling Realm.createObject(), -> new object will all fileds set to the default value -> ... suggested soule using copyToRealm() method
        
        If using String and boxed integer(Byte, Short, Integer, and Long) can have null primary keys unless the using Required annotation
      - Customizing Objects
        
        It is possible to use RealmObjects almost like POJOS by extending from RealmObject
      - RealmModel interface
        
        Extending the RealmObject base class is implementing the RealmModel interface and adding the RealmClass annotation
  - - - Simply declare a property with the type of one of you RealObject subclasses
      - Setting the RealmObject field null will clear the reference but the object will not be deleted from thre Realm.
    - - Using RealmList<> field declaration
    - - RealmResult<Persion> r1 = relam.where(Persion.class) .equalTo("dogs.name", "Fluffy") .findAll()
    - - using to support many-to-many relationships
      - Create by using LinkingObjects anotation in a final field
      - Querry (realmResults<Dog> brownFluffies) = realm.where(Dog.class) .equalTo("color", "Brown") .equalTo("name","Fluffy") .findAll()
      - RealmResults<Dog> dogs = realm.where(Dog.class).equalTo("persions.name", "Jane").findAll()
  - - - An asynchronous transaction is represented by the RealmAsyncTask object
      - should be use executeTransactionAsync() to execute a transaction in backgroud and transaction.cancle() in onStrop() UI
    - - RealmObjects are strongly tied to a Realm
      - We can create an object first and add it later using realm.copyToRealm()
  - - - Where() initiate a query represented by a RealmQuery
        
        after then can use:
        
        equalTo()
        
        notEqualTo()
        
        in("name", new String[]{"","",""...})
        
        like("name","ia?") or like("name", "?ill''")
        ...
      - logical operations
      - sorting
        
        Sort.DESCENDING...
      - Unique values
        
        dostinict("name")
      - Chaining Queries
        
        beteween("age", 13,20)
      - Auto-Updating results
      - Iterations & snapshots
      - Deletion
        
        Can delete the results of a query from the Realm
      - Create the query
        
        to ensure the query completed and RealmResults object is updated, you can register a RealmChangeListener -> unregister in onStop() or forcue load an asynchronous query by using findAllAsync() + realmResults.load()
  - - - Setting a default configuration in Application class -> will ensure that it is available in the rest of your code
    - - using assetFile("my.realm").readOnly()
    - - using inMemory() in realmConfiguration
      - create an in-memory Realm instead of saving it to disk
    - - a Dynamic realm is a variant of the conventional Realm that makes it possible to work with Realm data without using realmObject subclasses
      - ignore any configured schema, migration, and schema version
    - - will only work from Looper threads.
    - - purpose is native memory deallocation and file descriptors
  - - - Important: Realm, RealmObject or RealmResults instances cannot be passed across threads
        
        Can use an asynchronous query or asynchronous transaction
        To offload the operation to a background thread and bring any results back to the original thread for current threads
  - - - for lib dev
  - - - We recommend that you use a crash reporting tool (Ex: Crashlytics)
- - - - Java(Android)
      - C#(Xamarin, .NET)
      - Javascript(React native and Node.JS)
    - - Help for manager data synchronization, even handling, and intergation with legacy systems
      - It provides a single place to manage all communications, including legacy API transactivons
      - A key component is The Realm Node.js SDK
      - Components
        
        Sync engine
        
        Dashboard
        
        Auth System
        
        Access Control
        
        Objects Store
        
        Event framworkd