SQLite didn't accept `returning`

[Nisgrak]

Describe the bug

The in memory sqlite isn't working, didn't accept returning syntax.

Link to the blitz that caused the error

https://stackblitz.com/edit/mikro-orm-esm-repro?file=package.json

Steps to reproduce

1. Wait to finish the boot up and check the failed test in the console

Expected behavior

The test is successful

Parity with Local

• I have run the project in my local machine and I could not reproduce the issue.

Screenshots

Platform

Browser name  = Chrome
Full version  = 106.0.0.0
Major version = 106
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/106.0.0.0 Safari/537.36
performance.memory = {
  "totalJSHeapSize": 68413652,
  "usedJSHeapSize": 65796832,
  "jsHeapSizeLimit": 4294705152
}
Hash = d4ca26c86a8e75fb184ca97fc78f0c245928f6b1

Additional context

mikro-orm/mikro-orm#3655

[SamVerschueren]

It appears that the returning syntax is something new, which does not appear to be not present in our sqlite3 polyfill yet. I created an internal ticket to update the polyfill.

[Nisgrak]

Looks was released almost 2 years ago.

https://www.sqlite.org/lang_returning.html

The RETURNING syntax has been supported by SQLite since version 3.35.0 (2021-03-12).

Anyway, thanks!

[B4nan]

Any updates on this? it sounds like a simple dependency update, is there any blocker?

I wanted to start using stackblitz for reproductions, but this is blocking on our end as MikroORM now uses returning statements in sqlite driver.

[B4nan]

Let me ask one more time - if there is anything I can do to help move this forward, let me know. I would very much like to start using stackblitz for reproductions, but this is a real blocker for me.

[d3lm]

Hey! We haven't had a chance to update our polyfill yet. We keep you posted if we find time to do this.