If we use the "integer" JSON Schema type, we should save that as an INTEGER column, not a REAL column. Both will work for many numbers, but larger integers (like 2**63) can only be safely stored in INTEGERs. This should be a bit more reliable.
As of this patch, we don't have any integer types in our schemas, so this has no effect. However, that may change as we address upcoming issues.
Depends on #530.
If we use the "integer" JSON Schema type, we should save that as an INTEGER column, not a REAL column. Both will work for many numbers, but larger integers (like
2**63) can only be safely stored in INTEGERs. This should be a bit more reliable.As of this patch, we don't have any integer types in our schemas, so this has no effect. However, that may change as we address upcoming issues.