slouchpie

Vague idea - IndexedDB + Ecto

PWAs use a thing called IndexedDB

I was reading the docs this morning and thought how cool it would be if there was some package built on top of Ecto that could automatically convert a project’s existing Ecto schemas to “object stores” (that’s what they’re called).

Even in a new project, maintaining the object store schemas to accord with the Ecto schemas is a burden (Absinthe devs will know this pain). It would be cool if it could be automated.

You can see an example of how an object store is built here:

github.com/mdn/dom-examples

to-do-notifications/scripts/todo.js

main

window.onload = () => {
  const MONTHS = [
    "January",
    "February",
    "March",
    "April",
    "May",
    "June",
    "July",
    "August",
    "September",
    "October",
    "November",
    "December",
  ];

  // Hold an instance of a db object for us to store the IndexedDB data in
  let db;

  // Create a reference to the notifications list in the bottom of the app; we will write database messages into this list by

This file has been truncated. show original

I throw this vague idea into the void and see if anything resonates…

4 comments

#ecto #indexed_db

11 210 4

2025-10-12 12:09:27 UTC

Most Liked

garrison

Might be better to look towards OPFS instead. I don’t have a source off the top of my head but I have heard many times that IndexedDB is, for various reasons, very unpleasant to deal with. My understanding is that going forward OPFS will be better (and is now widely available).

Post #2

bartblast

Creator of Hologram

I have something along these lines planned for the local-first stage of Hologram. I agree with @garrison that OPFS is probably the way to go here.

One thing to keep in mind though – it needs to be a little more involved than just storing data on the client. You’d probably want:

Auto-sync between client and server
Managing schema and data migrations on the client-side
Deciding what subsets of data to sync to the client-side (not everything should/can be synced)

Post #3

slouchpie

@garrison Yes, OPFS looks much better. Thank you!

@bartblast Very exciting to hear about local-first plans. I might play with the OPFS stuff myself just to see what is possible.

Post #4

Where Next?

View thread on forum (has 4 responses!)

ecto

indexed_db

Home Chat & Discussions>Discussions

#ecto #indexed_db

11 212 4

Last post

Vague idea - IndexedDB + Ecto

slouchpie

Vague idea - IndexedDB + Ecto

Most Liked

garrison

bartblast

slouchpie

Where Next?

Popular in Discussions

Comparing the fairness and real-time performance of schedulers in Erlang and Go

Advent Of Code libraries and frameworks

Which Elixir version(s) are you (still) using on your non-pet projects?

A case for inline type annotations

How is Firefly going?

The real problem isn't "how do we organize files better?" but rather "why are we organizing files at all?"

What’s wrong with Umbrella Apps?

I used Claude Code +Fluxon UI to generate real world page samples

Is it common to create accessor functions for struct fields?

What libraries do you feel are missing in the Elixir ecosystem in 2024 compared to others like Python or PHP?

Other popular topics

Phoenix 1.4.0 released!

Oban - Reliable and Observable Job Processing

Updating a field using Ecto one-liner?

What do you think of Gleam compared to Elixir?

How is it possible to get 2 million websocket connections when you have 65536 available ports?

Enum.map over list of key/value pairs with a map as the value

IntelliJ Elixir - Elixir plugin for JetBrain's IntelliJ Platform

(EXIT) no process: the process is not alive or there's no process currently associated with the given name, possibly because its application isn't started

Proper use of Task.async?

Using VSCode on multiple monitors

Chat & Discussions>Discussions

Latest on Elixir Forum

Sponsor Spotlight

Our Sponsors

Categories:

Sub Categories:

Forums

Our Sponsors

We're in Beta