Message parsing optimization

[tdrz]

This changes a bit the return of the parseResults() function in certain cases - see the updated basic test testEsmAndCjs.

[github-actions]

Built bundles:

• Postgres WASM: https://github.com/electric-sql/pglite/actions/runs/12775790078/artifacts/2430706933
• Interim build files: https://github.com/electric-sql/pglite/actions/runs/12775790078/artifacts/2430707082
• PGlite: https://github.com/electric-sql/pglite/actions/runs/12775790078/artifacts/2430740420
• Demos: https://github.com/electric-sql/pglite/actions/runs/12775790078/artifacts/2430764196

[github-actions]

🚀 Deployed on https://67868c4d430dfc85b0e00916--pglite.netlify.app

[samwillis]

Nice, thanks! Looks like it solved something with affectedRows in the tests too?

We should add another changeset

From the root of the repo run pnpm changeset and follow the instructions. Everything is a patch change at the moment.

[tdrz]

Looks like it solved something with affectedRows in the tests too?

In some cases, like

      INSERT INTO test (name) VALUES ('test');
      UPDATE test SET name = 'test2';

affectedRows was not returned.

I hope that no other code was relying on the fact that it was not present.

Also, note this case:

// parse.ts
  if (resultSets.length === 0) {
    resultSets.push({
      rows: [],
      fields: [],
    })
  }

No affectedRows is returned. I have set it to affectedRows: 0