Environment

Knex version: 0.21.1
OS: docker node:latest

I'd like to be able to write my migrations (and seed) files as es modules with the .mjs file extension like I'm doing with all my other javascript files.

I'd like to be able to run these migrations from within node (not via the cli) like this:

db/migrations/00001-users-table.mjs:
    export const up = knex => knex.sche

Hi!

I tried out MikroORM in an NX Workspace, and to use it there, I see a blocker.

Really easy to try out, there is a create-nx-workspace npm package out there and it can scaffold up a workspace with nestjs in no time

In an NX Monorepo setup, every single project uses the same top-level package.json, but MikroORM CLI relies on the config specified in the package.json.

.

RediSQL support multiple statements in the same "EXEC", hence it is possible and correct to do something like:

REDISQL.EXEC DB "INSERT INTO foo VALUES(1,2,3); INSERT INTO bar VALUES(2,3,4);" 

Which is quite convenient when mixed with BEGIN, COMMIT and ABORT instruction.

One problem is that all the statements are first prepared all together, and then executed, all together.

This

MMEX version:

• 1.3.6
• 1.3.5
• 1.3.4 or older
• 1.4.X

Note: bug reporters are expected to have verified the bug still exists
either in the last stable version of MMEX or on updated development code
(master branch).

Operating System:

• Windows
• Mac OSX
• Linux

Description of the bug

Application crash when selecting 'Relocate Payee' when i

Describe the bug
"Select file" for the socket file path shows a local file chooser, even when I'm in a remote workspace and thus would expect to look for a file on the remote system.

To Reproduce
Try selecting a socket file path when you are using a remote vscode workspace

Expected behavior
File picker that shows remote files

**Desktop (please complete the following informa