Brandon

This looks like a great simplification, and will save a lot of ceremonial code, especially since my use case is really only to ILogger the raw SQL to app insights...

Sure I was affirming that the flexibility is great. I was only recommending to also offer the default keys as constants…to save all consumers from having to do this themselves,...

Sure, the compiler will replace all instances of a constant with the literal. My recommendation was only concerning readability and even a little discoverability benefit….ultimately a set of provided constants...

Yep that makes sense! Thanks…yeah it’s a small thing but sometimes super useful.

Per our conversation on Gitter, our initial discussion yielded the following findings: 1. Microsoft documentation states for `DbType Enum` it says `DbType.Time (17) -- A type representing a SQL Server...

**Good News:** As discussed on Gitter, we cannot easily change the legacy code base from using `System.Data.SqlClient` (yet; it's on our strategic plan though), however we were able to resolve...

@mikependon this is great, thank you so much for the complement on my repo! In fact you have already read my mind. I wanted to ping you soon about the...

Sorry about that broken link, I had to rename by request from the HotChocolate core team...they want to keep any other uses of their namespace out of Nuget so renaming...

This could be potentially used to support Cursor based paging as laid out by Relay spec (extension of GraphQL) for cursor based movemeent forward and backward through a result set....

Also as a note on this particular feature request for "SkipQuery"... it's really just a variation of BatchQuery without the page calculation -- both can be mapped to starting row...