rethinkdb_ecto
rethinkdb_ecto copied to clipboard
Ecto virtual fields
When running insert/1 on a changeset, the shim does not appear to respect the virtual: true setting in the schema, and inserts the virtual fields with their data (eek) into the database.
I'm having some trouble searching the Ecto docs to find at which point the virtual fields are actually stripped out. By the time Ecto.Changeset.apply_changes(changeset) is applied to return the model for insertion, the virtual fields are still present in changeset.changes.