Insert String, Integer, Map, List in a jsonb PostgreSQL column

You still have to wrap any data you want to persist in a map, like this:

%{string_field: "toto"}
%{integer_field: 12}
%{list_field: [1,2]}

Obviously, replace the field names with what you need.

It seems not appropriate from my point of view.

The DB column declaration says it’s a map, not any random piece of data you can throw at it though.

Can you describe your desired use case?

It’s an issue from Ecto ORM as it is possible to do it directly through PG method.

The type :json should exist in Ecto.Schema.Type

Can you show your table definition in raw SQL?

Interesting. I would guess PostgreSQL automatically wraps things in maps below but I haven’t read up on it.

Thanks for the tidbit.

You can always create your own. The ecto type is a map type not a json one. In the end ecto is not bound to any db at all and it makes way more sense to have types, which align well to elixir than ones that align well with a certain database.

I think wrapping into single key shouldn’t affect any business logic.

%{data: "toto"}
%{data: 12}
%{data: [1,2]}

Actually, to avoid struct.data.data just name it jsonb! so you retrieve it struct.data.jsonb .. I think it makes sense.

@50kudos: ok, now perform jsonb search query on 500_000_000 rows in order to return 1_000_000 rows. Just few lettters, but they would be repeated way too often. It’s not really scalable option. Of course one thing like that would not force 100% server usage, but we should develop best solution and not only working solution.