Prebuilt Realm Db

[usefulBeeing]

Just came across realm-dotnet, as an alternative to sqlite, and wondering if it might fit my needs. I have a simple scenario where I have a couple of tables that will rarely get changed, with a couple of hundred records at most. In a sqlite scenario, I would usually create the database and tables using a tool like sqlitebrowser for example, then ship the prebuilt database, tables and records with the application.

I can't wrap my head around Realm as a local storage solution yet but curious if it could handle a prebuilt objects scenario like this one, and how?

Thank you.

[peppy]

In our experience this should work just fine!

[uixiu]

My opinions:

Realm database is a better alternative to SQLite even for medium sized database.

PROS:

You get a out of the box

• A good enough Database explorer, with html links to sub collections (easy navigation)
• Object oriented like experience
• No need for SQL experience
• No need for ORMs and its quirks, ( ORM needs knowledge and experience)
• Observable objects(entities) and tables (collections) wherever changes came from.
• Ultra fast readings.
• Rock solid database.
• LINQ implemented querying.
• "Zero" copy architecture, which leads to minimal RAM consumption.
• You pay (in ressources) only for what you actually consume. Consequence of the previous point .
• Multiple Realms in different locations (mobile or desktop) can be automatically synchronized (MongoDB subscription).
• You pay only for the synchronized data, not for the offline/local reading/writing.

CONS:

• NEEDS some time for initial adjustments
• Threading model is not trivial: Consequence of the previous point. If you want access your realm from another thread, you should create another realm for the same database on the same new thread then operate on it from there. The main thread's Realm will automatically be synchronized at the end, eventually needs only a Refresh method (I've never needed it)
• Every property change should occure in a transaction, which sometimes can be awkward, especially with UI components. But there are workarounds for this. Feel free to ask your questions here.

---

As for your question you can ship your database with your application just like SQLite.

If there's a database file at the RealmConfig specified path, it will be loaded in the Realm. If not, a new empty one will created with a default schema costructed by the object model you define (objects implementing IRealmObject)

[usefulBeeing]

Your response was an excellent starting point @uixiu. I found the exact answer to my question while exploring the mongodb documentations under Bundle a Realm. Thank you for your efforts.

[uixiu]

Feel free to ask here if you have questions.

[uixiu]

Hi @usefulBeeing
I wanted to let you know that I came across a recent MongoDB announcement
https://www.mongodb.com/docs/atlas/device-sdks/deprecation/#std-label-device-sdks-deprecation

The announcement mentions the deprecation of device SDKs (Realm Sync), which could potentially impact Realm in the future. If you plan to rely on device sync functionality, you might want to start exploring alternative solutions.

[usefulBeeing]

Thanks for the heads up @uixiu. I appreciate it.