Graph-Based Ceramics

I would definitely use a simple relational model for this. Or probably in practice just download the whole dataset and do everything locally because it's going to be so small.

But I suppose this is an ad for the writer's graph database anyway.

What an excellent ad for SQLite, where you could do this with a simple schema:

    Table 1:   

    Table 2:   

That's.. it.

Location specifies where the combo is applied to the part; priority specifies ordering of the glaze layers (glazes whose order doesn't matter have the same priority).

The only thinking that needs to be done is understanding that you don't mix glazes and combinations in a single project, but a project has a set of combinations associated with it, some of which may only have one glaze.

Writing the requisite SELECT queries (getting all pieces that use a glaze, or vice versa) is left as an exercise to the reader (which, I hope, is straightforward - but the same can be said of the schema).

This article does a lot of mental gymnastics to avoid using a relational database to store relations. NoSQL has its places (e.g. sometimes, a KV store is a KV store), but this isn't it.

Sometimes I feel like the NoSQL hype did some collective damage to the way people think about data. But then again, I'm not a database architect, so what do I know.

Cool, another computer nerd into ceramic and glazes!

Glazes is actually glass where you mix all kinds of powdered element from the periodic table and melt them at 1200C to hopefully get a result you like. A unusual kind of chemistry.

I am more interested in the glazes and the results he got than the crud app and the DB. Just read it in diagonal, but I don't see why a simple Django app wouldn't take care of this easily (with admin) and you use sqlite for local use case.

CNC pottery is so much fun. Highly recommend getting into Rhino / Grasshopper if you aren’t already. You can go as deep as you want, and programmatically generating gcode means the world is your oyster (or at least the clay is, or at least when it cooperates)

You would have been done with maybe 1/10 the code if you went with SwiftData and targeted ios17 as the base os as that is also a graphdb, you don’t really need a server for this type of app. Everything local would be good enough.