Possibly use raw SQL to convert to jsonb (maybe not always) about ash_postgres

[zachdaniel]

Its an interesting idea, we could potentially do something like this by default. I think its reasonable that some migrations will have to have manual intervention, but this seems like something we could potentially detect and provide a better default for.

[zachdaniel]

Yeah, but a string is a valid jsonb. So my point is even with USING column:jsonb it will still not be an actual object under the hood.

[zachdaniel]

Yeah, exactly. Its possible that in the future we could do it with something interactive in cases we can detect an issue, but the juice is unlikely to be worth the squeeze.

[zachdaniel]

In this case, though, it would produce a jsonb string and not a map though.

[dmitriid]

The migrations generator produced modify :settings, :jsonb for me when I changed attribute type from string to map🤔

[dmitriid]

Ah! I see what you mean.

I missed this because in my case I was storing Jason.encoded strings anyway :) But if there were other strings, it would either fail, or would fail on read 🤔

No idea how to solve this properly besides generating warnings or comments during migration or when generating migrations.

[zachdaniel]

Yeah, I mean honestly thats what happens when you run the migrations, the data store tells you that you can't actually do that transition and have to figure out some other way to do what you want. I'm not sure if the migration generator should try to figure this one out since it can't know what the right answer is.

[zachdaniel]

I think we can't reliably do this kind of thing currently. Folks will need to edit the migrations themselves.

[dmitriid]

awww shucks :(

Well, it will probably affect a very small number of migrations anyway, and the solution is quite easy.