<https://github.com/MeltanoLabs/target-postgres/is...
# singer-target-development
v
https://github.com/MeltanoLabs/target-postgres/issues/168 What do folks think about a schema like
Copy code
{"type": "SCHEMA", "stream": "Tenant__History", "schema": {"type": "object", "additionalProperties": false, "properties": {"Id": {"type": "string"}, "CreatedDate": {"anyOf": [{"type": "string", "format": "date-time"},  "OldValue": {}, "NewValue": {}}}, "key_properties": ["Id"], "bookmark_properties": ["CreatedDate"]}
Specifically
OldValue
and
NewValue
should we just cast these to strings, or should this fail? https://github.com/singer-io/getting-started/blob/master/docs/SPEC.md#schema-message isn't super clear to me, I think JSON Schema's spec says
{}
just means anything goes. So maybe we should accept this and just convert the value to a string?
e
Yeah I think the target should just
json.dumps
those fields