Repo.load does not assign a value to virtual fields

Questions / Help
,
1

Hello,

I have results from a raw SQL query (using Postgres). I am trying to use Repo.load to map the results to an existing schema in my application. All columns are mapped except one column that is a virtual field. The column exists in the query result (as a string because it is from a raw query) and has values in each row. There is a 2018 post here, but it is not conclusive. Someone said that it is a bug if this happens. Anyone knows if this bug has been fixed? If not what is a good workaround?
I am using {:phoenix_ecto, "~> 4.5"}, {:ecto_sql, "~> 3.13"}`.

2

I would appreciate some advice from those who have experience. Should I just abandon the idea of trying to load it into a schema and use standard maps instead for this use case?

Thank you.

3

You might want to raise the issue in the Ecto github repository, to me it sounds like a bug.

4

Thank you. I will do that.