[Question] WriteAsync default behaviour
See original GitHub issueGreetings. I have a rather simple question. What happens when you try to call _client.Client.WriteAsync(point, "someNonexistentDb")? Will one be created for you? Or nothing will happen / an exception will be thrown?
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
c# - WriteAsync with timeout
For example that is the default behavior of a FileStream if you don't pass in FileOptions.Asynchronous to the constructor.
Read more >Default behavior of system.tag.write in 8.0.x - Ignition
writeAsync methods in 8.0, my understanding is that system.tag.write was deprecated, but we still use it in our logic and it still works...
Read more >system.tag.writeAsync - Ignition User Manual 8.0
Asynchronously writes values to Tags at specified paths. The script will not wait for the write operation to complete before moving on, but...
Read more >Will calling HttpResponse.WriteAsync() cause ...
Yes this is the intended behavior. AspNetCore does not buffer responses by default, so WriteAsync auto-flushes, (.NET Framework did in some ...
Read more >Make ConfigureAwait(false) the default behaviour for Tasks
The default behaviour when await-ing a Task is to return to the caller thread. This behaviour was designed in the time of WPF...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@Svetomechc That entirely depends on the influx config.
I think you should probably get an exception form the influx response though.