No longer able to provide SQL parameters to `ExecuteAsync()` since 6.0.0

[PeterN]

With NPoco 5.7.1, I used to be able do the following. (This is a dumbed-down example, the real query is more complex.)

await db.ExecuteAsync(@";
      select @created, @modified, @id",
      new
      {
          created = DateTime.UtcNow,
          modified = DateTime.UtcNow,
          id = 1
      });

Since NPoco 6.0.0, a cancellationtoken parameter is added, and the code no longer compiles with the following error.

error CS1503: Argument 2: cannot convert from '<anonymous type: System.DateTime created, System.DateTime modified, int id>' to 'System.Threading.CancellationToken'

The function's signature is changed from Task<int> ExecuteAsync(string sql, params object[] args) to Task<int> ExecuteAsync(string sql, object[] args, CancellationToken cancellationToken = default(CancellationToken)), so without the params part it no longer works.

I don't see anything about this change in the release notes, so I'm not sure what I'm meant to be doing differently now.

[ahazelwood]

The params keyword in the previous version allowed the object to be accepted as the first parameter as it collected all parameters after the sql. I believe you just need to wrap it in an object array and it should then work.

await db.ExecuteAsync(@" select @created, @modified, @id", new object[] { new { created = DateTime.UtcNow, modified = DateTime.UtcNow, id = 1 } });

[mmooney]

I just ran into this too, that is pretty annoying. This is going require so much more repetitive typing now.

[ahazelwood]

@mmooney I understand, however I believe he's trying to handle passing in CancellationTokens so it follows best practices at the end of the Async methods.

[makingbloke]

I was in a similar situation recently and researched this. The recommendation from MS is this (sorry so don’t have the source to hand): If you are not using Params then cancellationtoken is always the last argument. If you are using params then it goes before the params object[] argument parameter. It would be a breaking change but this would probably be the solution.

…

On Fri, 9 Jan 2026 at 15:57, ahazelwood ***@***.***> wrote: *ahazelwood* left a comment (schotime/NPoco#721) <#721 (comment)> @mmooney <https://github.com/mmooney> I understand, however I believe he's trying to handle passing in CancellationTokens so it follows best practices at the end of the Async methods. — Reply to this email directly, view it on GitHub <#721 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABPMCPI5RCNEJIZZOIMAWGD4F7FXFAVCNFSM6AAAAACNMVV66WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMRZGUYDIMRTGY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[ahazelwood]

@makingbloke Currently I use a custom object that utilizes npoco under the covers, so I can handle this either way. I will leave it up to @schotime to determine what he thinks makes the most sense based on feedback he's gotten.