Description
If a custom ITypeSerializer is provided which doesn't also implement IStreamingTypeDeserializer, we should fallback to reading as a block and emulate streaming on the IQueryResult API surface. This will make implementing custom deserializers easier if streaming is not required.
Attachments
Issue Links
Activity
Field | Original Value | New Value |
---|---|---|
Status | New [ 10003 ] | Open [ 1 ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Description | If a custom ITypeSerializer is provided which doesn't also implement IStreamingTypeDeserializer, we should fallback to reading as a block and emulate streaming on the IQueryResult API surface. This will make implementing custom deserializers easier it streaming is required. | If a custom ITypeSerializer is provided which doesn't also implement IStreamingTypeDeserializer, we should fallback to reading as a block and emulate streaming on the IQueryResult API surface. This will make implementing custom deserializers easier if streaming is required. |
Resolution | Fixed [ 1 ] | |
Status | In Progress [ 3 ] | Resolved [ 5 ] |
Description | If a custom ITypeSerializer is provided which doesn't also implement IStreamingTypeDeserializer, we should fallback to reading as a block and emulate streaming on the IQueryResult API surface. This will make implementing custom deserializers easier if streaming is required. | If a custom ITypeSerializer is provided which doesn't also implement IStreamingTypeDeserializer, we should fallback to reading as a block and emulate streaming on the IQueryResult API surface. This will make implementing custom deserializers easier if streaming is not required. |
Story Points | 1 |