🐛 BUG: .run() throws D1 Error in cloud

[AlexBlokh]

What version of Wrangler are you using?

2.4.2

What operating system are you using?

Mac

Describe the Bug

await env.DB.prepare('insert into users (name, email) values (?, ?) returning *').bind(name, email).run();

throws Exception in cloud

"exceptions": [
    {
      "name": "Error",
      "message": "D1_ERROR",
      "timestamp": 1668795822085
    }
  ]

These three below work as expected in cloud

await env.DB.prepare('insert into users (name, email) values (?, ?) returning *').bind(name, email).all();

await env.DB.prepare('insert into users (name, email) values (?, ?) returning *').bind(name, email).first();

await env.DB.prepare('insert into users (name, email) values (?, ?) returning *').bind(name, email).raw();

All four requests do work as expected locally

[Skye-31]

According to the docs, .run() should be used for queries that return no results. While it probably shouldn't be a generic error - it should be returning an error.

[AlexBlokh]

It may or may not fail, it's completely up to the API design, at least should be consistent locally and in the cloud

[Skye-31]

Agreed

[penalosa]

Hi—thanks for reporting this! That's definitely a local/remote behaviour mismatch that we should fix. In the meantime, you can often get more helpful error message by checking error.cause (in this case the error message is ERROR 9007: SQL execute error: Execute returned results - did you mean to call query?:

export default {
  async fetch(
    request: Request,
    env: Env,
    ctx: ExecutionContext
  ): Promise<Response> {
    await env.DB.exec(
      "create table if not exists users (name text, email text);"
    );
    try {
      await env.DB.prepare(
        "insert into users (name, email) values (?, ?) returning *"
      )
        .bind("a", "b")
        .run();
    } catch (e) {
      return new Response(e.cause);
    }
    return new Response("Hello World!");
  },
};