Possible bug in ecto? Asking here first for clarification about money_sql HOT 3 CLOSED

Turns out I can't work around this. Adding type/0 to the composite type seems to make Ecto think its a non-parameterised type and therefore other bad things happen.

from money_sql.

Confirmed it was an Ecto bug which is now fixed on the main branch. I confirmed is works in my tests.

I expect this will be fixed when Ecto 3.6 comes out. Until then, if there is no other way, I recommend you use ecto directly from GitHub using:

# Your query should look like this
# init_options is either `[]` or a keyword list of options
# you would pass to the `:field` definition on an ecto
# schema
    query =
      from(
        organization in "organizations",
        select: %{
          total: type(sum(organization.payroll),
            ^Ecto.ParameterizedType.init(Money.Ecto.Composite.Type, init_options)
          )
        }
      )

# Which basically is the same as:
    query =
      from(
        organization in "organizations",
        select: %{
          total: type(sum(organization.payroll),
            ^{:parameterized, Money.Ecto.Composite.Type, []}
          )
        }
      )

# mix.exs
def deps do
  ...
  {:ecto, github: "elixir-echo/ecto", override: true},
  ...
end

Closing this issue for now, let me know if there is anything else I can help with.

from money_sql.

Thats definitely curious and I wonder if it is indeed an Ecto bug. I'll do some digging. In the meantime I can workaround this since I need to push an update today for issue #14.

Thanks much for the issue and sorry for the inconvenience. Moving to a parameterised type has proved more problematic on edge cases than expected.

from money_sql.