This is a breaking change

I have a feeling we are relying on Value being jsonb at the moment in CircuitHub code. Could you check that? Hopefully grepping for Column f Value and then checking the current schema will point you in the right direction. Generally speaking I think the current behavior is correct - the PostgreSQL json type preserves whitespace (iirc), but Value doesn't - so it's not quite the same type.

Maybe the right thing to do in that case is have JSONEncoded not go directly via the Value instance

How about this instead @ocharles ?

Yea this looks good - I'll have to remind myself how TypeInformation works! Could we write any tests for this?

Actually I'm going to inline some of this to make it a bit clearer and mirror JSONBEncoded

SGTM!

I've added a test case as well