RowVersion not working with GraphQl Client

[noufionline]

When I try to use byte[] (Timestamp column) its throws the following exception.

GraphQL.ExecutionError: Input string was not in a correct format.
---> System.FormatException: Input string was not in a correct format.
at System.Number.ThrowOverflowOrFormatException(ParsingStatus status, TypeCode type)
at System.Byte.Parse(String s, IFormatProvider provider)
at GraphQL.ValueConverter.<>c.<.cctor>b__1_1(Object value)
at GraphQL.Types.ByteGraphType.ParseValue(Object value)
at GraphQL.Execution.ExecutionHelper.AssertValidValue(ISchema schema, IGraphType type, Object input, String fieldName)
at GraphQL.Execution.ExecutionHelper.AssertValidValue(ISchema schema, IGraphType type, Object input, String fieldName)
at GraphQL.Execution.ExecutionHelper.AssertValidValue(ISchema schema, IGraphType type, Object input, String fieldName)
at GraphQL.Execution.ExecutionHelper.AssertValidValue(ISchema schema, IGraphType type, Object input, String fieldName)
at GraphQL.Execution.ExecutionHelper.AssertValidValue(ISchema schema, IGraphType type, Object input, String fieldName)
at GraphQL.Execution.ExecutionHelper.AssertValidValue(ISchema schema, IGraphType type, Object input, String fieldName)
at GraphQL.Execution.ExecutionHelper.GetVariableValue(Document document, ISchema schema, VariableDefinition variable, Object input)
at GraphQL.Execution.ExecutionHelper.GetVariableValues(Document document, ISchema schema, VariableDefinitions variableDefinitions, Inputs inputs)
at GraphQL.DocumentExecuter.BuildExecutionContext(ISchema schema, Object root, Document document, Operation operation, Inputs inputs, IDictionary2 userContext, CancellationToken cancellationToken, Metrics metrics, IEnumerable1 listeners, Boolean throwOnUnhandledException, Action1 unhandledExceptionDelegate, Nullable1 maxParallelExecutionCount)
at GraphQL.DocumentExecuter.ExecuteAsync(ExecutionOptions options)
--- End of inner exception stack trace ---

[noufionline]

@sungam3r

I have already opened an issue related to this.

Input type with RowVersion is not working (#1534)

From the client side I am facing issue.

[rose-a]

So basically the server complains about a bad input variable... can you verify what's coming in on the server side and compare that to what you'd expect?

[noufionline]

@rose-a
While using the graphql UI List is received but from the client the server receives 64bit string

[rose-a]

I guess the easy workaround would be converting the byte array to a list on the client before sending it.

I'm not yet sure if it would be a good idea to alter the serialization of all bytearrays...

[rose-a]

What are you trying to submit using that bytearray? Maybe another representation would be better suited?

[noufionline]

@rose-a
I am updating Lookup Items in SQL Server database. Each table contains a TimeStamp column which keeps track of change tracking (Concurrency). In C# Timestamp columns are represented as byte[].

[sungam3r]

I have already opened an issue related to this. Input type with RowVersion is not working (#1534)
From the client side I am facing issue.

My first comment was graphql-dotnet/graphql-dotnet#1534 (comment) . It would save us a lot of time.

[rose-a]

Ok, IMO you should not use a byte[] type to convey this information. The natural way would be using a DateTimeGraphType on your API and convert this back and forth in C#. Alternatively use a long if you just want to have an opaque timestamp on your API.

Those are both formats which can be well represented in JSON.

You should avoid binary fields in your API.

[sungam3r]

While using the graphql UI List is received but from the client the server receives 64bit string

@rose-a If so, I think you should think about how to serialize byte arrays. After all, you do not serialize arrays of strings or other types (ints) like base64 string? Right?

[rose-a]

@sungam3r https://discuss.jsonapi.org/t/handling-binary-data/315

[sungam3r]

You should avoid binary fields in your API.

In principle, I agree. But I was interested in another question. Do I understand correctly that the serialization format of int[] and byte[] is very different?

[rose-a]

Yes it is, but byte[] can either represent "a list of bytes", but in most cases is indeed binary data, as it is in @noufionline's case.

Converting the byte[] to a List<byte> would clearly express the intend to send a "list of bytes" instead of binary data and will most likely automatically result in the desired output from the JSON serializer.

In this case you also would use an EnumerationGraphType on the server side, wouldn't you?

[noufionline]

Please find some graphics to get a better idea of my issue

[sungam3r]

@sungam3r https://discuss.jsonapi.org/t/handling-binary-data/315

I look from the other side. The server declares the schema. This schema has a field with input argument of type [Byte!]. It is a array of some custom scalar named Byte. If the server declared field of type Bytes or Binary or something else but not array, then a discussion about the format would still make sense. Now the graphql-client just violates the server API.

[rose-a]

@noufionline As I already said, create your variables object like so:

Variables = new { Lookup = item.ToList() }

This will tell the JSON serializer that you want to send a list of bytes!