I’ve created an Opponent model that has several fields associated with it, each of which represents an actual or computed value. You can check out the whole file as it exists right now here , but the schema itself looks like this: schema "opponents" do field :name, :string f…

Assuming PostgreSQL as a database. You have 2 options how to make it “right”: Views in the DB (potentially materialised) If you are on Postgres 12+ then you can use generated fields Both will make your application much clearer and, at least logically, normalise your data.

[image] Linell: I’ve actually got two questions here: What is the right way to ensure that my autosum_fields method runs whenever the opponent is updated? Is there a better way to handle the actual updates? I know I’m doing more updates than is required right now because it’s happening on a pe…

[image] hauleth: Assuming PostgreSQL as a database. You have 2 options how to make it “right”: Views in the DB (potentially materialised) If you are on Postgres 12+ then you can use generated fields Both will make your application much clearer and, at least logically, normalise your data. …

[image] Linell: How can I get fields for this record that aren’t part of the changeset’s changes? Ecto.Changeset — Ecto v3.14.0 get_field gets the value from changeset and if the field is not present in changes, then it gets it from the record.

[image] Linell: When you say doesn’t write directly to the calculated fields, do you mean that this approach would cause problems with being able to have those values as user input as well? Yes - if the fields are writable directly, you’ll need to decide what happens when incompatible paramet…

Creating Autosumming Fields

Questions & Help Questions

shankardevy September 11, 2020, 3:25am 5

get_field gets the value from changeset and if the field is not present in changes, then it gets it from the record.