BUG: Different responses when running a D1 query in the cloud and the local mode

[jiripospisil]

What version of Wrangler are you using?

2.4.2

What operating system are you using?

Linux

Describe the Bug

Hello! Consider the following code:

export default {
  async fetch(
    request: Request,
    env: Env,
    ctx: ExecutionContext
  ): Promise<Response> {
    await env.db.exec(
      "create table if not exists foos (value text);"
    );

    const result = await env.db.prepare(
      "insert into foos (value) values (?)"
    ).bind("from param").run();

    return new Response(JSON.stringify(result));
  },
};

When ran in the cloud, the response looks like this:

{
    "meta": {
        "changes": null,
        "duration": 9.485032001510262,
        "internal_stats": null,
        "last_row_id": null,
        "served_by": "primary-78d95a04-af3b-430b-8bd5-0196cf0c6331.db3"
    },
    "results": [],
    "success": true
}

However then running in the local mode (npm start -- --local --persist), the response is different:

{
    "changes": 1,
    "duration": 15.273903001099825,
    "lastRowId": 17,
    "results": null,
    "served_by": "x-miniflare.db3",
    "success": true
}