ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Databases & messaging · #realm
Goal I want to pass a managed Realm object from the main thread to a background worker so a heavy write transaction does not block the UI, while keeping the object usable for reading its current field values. Constraint and uncertainty My understanding is that Realm managed objects are thread-confined: an instance obtained on one thread cannot be used on ano
Schema Versioning in Atlas Device SDK When updating a local database schema in Realm, increasing the schemaVersion typically triggers a migration process during the Realm.open() call. If the version is incremented in the code but no migration block is provided to handle the structural changes, the SDK fails to open the file. Migration Constraints For small a
Goal: Safely retry a Realm write after a transient failure without creating duplicate persisted records. Constraints: Realm aborts the transaction on error, primary‑key upserts prevent local duplicates, but Realm Sync may still record separate change entries and transaction‑abort guarantees differ between Core versions and language bindings (Java, Swift, Kot
kotlin