Handle {:array, $type} types in Migrator #9
Conversation
Previously, a ecto type like {:array, :string} or {:array, :map} would
be fed into Code.ensure_loaded?/1, raising an argument error. While
it would be nice to be able to handle array types with encoded members,
ecto does not seem to handle the encoding to postgres nicely, and having
postgres report the field as an array of binaries leaks more information
than just having a binary type for the field and using Cloak.Ecto.Map to
wrap the data in a way that can be turned back into the list you want by
the app.
Ignores array types as far as Migrator is concerned
|
Would you mind sharing a copy of the error that you got when trying to use While I agree that using the |
|
@danielberkompas Sorry for the delay. I went back and retried the other way with just protecting the |
|
@danielberkompas Pushed up the revised version with an additional test to cover arrays of encrypted values. Feel free to squash it down on merge, since it still has the intermediary state and merge commits in there. |
ACBullen
changed the title
|
Fixed in #38 |
1 similar comment
|
Fixed in #38 |
Previously, a ecto type like {:array, :string} or {:array, :map} would be fed into Code.ensure_loaded?/1, raising an argument error. While it would be nice to be able to handle array types with encoded members, ecto does not seem to handle the encoding of arrays of binaries to postgres nicely, and having the database report the field as an array of binaries leaks more information than just having a binary type for the field and using Cloak.Ecto.Map to wrap the data in a way that can be turned back into the list you want by the app.