Database-Tool | Database Tool for Linux/Termux

As @iravinandan said you need to set up a tunnel.

Publishing a port alone won't help as all incoming requests are going through an http proxy.

If you dig CNAME .githubpreview.dev you will see it's github-codespaces.app.online.visualstudio.com. You can put anything in the githubpreview.dev subdomain and it will still be resolved on the DNS level.

The proxy relies on HTTP Host header to route the request to correct upstream so it will work for HTTP protocols only.

To use any other protocol (MongoDb wire protocol in your case) you need to set up a TCP tunnel from codespaces to your machine.

At the time of writing the default Node + Mongo codespace uses Debian buster, so ssh port forwarding would be the obvious choice. In the codespace/VSCode terminal:

The process name for notepad.exe is notepad. Update

There is a substantial difference between the function and procedure.

Both get parameters, but only function returns a value.

So basically a function can be called in a select statement or in a PL/SQL block in an assign statement. See example below.

Only a procedure can be simple called as you do it.

Some elementar information abour functions and procedures and their distinctions:

what-is-the-difference-between-function-and-procedure-in-pl-sql

functions-vs-procedures-in-oracle

Examples

Normally scripts auto exit at the end. Try to omit -noexit parameter from argumentlist and delete exit at the bottom of the script. For me, there is no sense to call a script with -noexit and put exit at the end of it. Without these all will automagically work.

If you want to examine what is going on during script writing, you can put eg. a timeout /t 90 command at the end, so you get 90 seconds to examine output before it auto closes.

• The 8191-character limit applies to the interactive command line and calls to cmd.exe's CLI (via cmd /c)

• It does not apply to commands invoked from batch files - there the limit is close to^[1] 32KiB (32,768) characters.

  • However, it still seems to apply selectively to cmd.exe's internal commands, such as echo; by contrast, a call to an external program such as powershell.exe is not affected (though it is possible for specific external programs to have their own, lower limits).

As an aside:

As clever as the linked method of converting PowerShell scripts to batch files is, the resulting batch files lack support for arguments to be passed through to the PowerShell code, and adding support for that would be impractical (it would require Base64-encoding the arguments too, at invocation time, which isn't possible from a batch file except with the help of non-built-in utilities).

• If your script / batch file is written to either require no arguments on invocation or to prompt for them interactively (as in your case), this limitation is not a concern.

• However, you may want argument support for any of the following reasons:

  • To allow calling the batch file from cmd.exe (Command Prompt) with arguments.
  • To allow calling with arguments from other environments that support passing arguments, notably Task Scheduler and the Windows Run dialog (WinKey-R).
  • To make the batch file support drag-and-drop (which implicitly passes the dropped files' paths as arguments).

As for the overall reason to wrap PowerShell code in batch files:

• Batch files (.cmd, .bat) can be launched directly, as if they were executables, system-wide.
• By contrast, this is not supported for PowerShell scripts (.ps1), which from outside PowerShell must be invoked via an explicit call to the PowerShell CLI; note that systems may be configured to categorically prevent execution of .ps1 scripts - see next section.

If you do need argument support in your batch file, the best - but inconvenient - solution is to distribute two files:

• the original *.ps1 file...
• and a companion batch file, with the same base file name, to be placed in the same directory - which can be invoked from outside PowerShell - whose sole purpose is to invoke the *.ps1 file via powershell.exe with pass-through arguments.

E.g. foo.cmd would accompany foo.ps1, with the following - invariant - content:

in your raspberrypi dupm your db with:

Finally got it working: I tried sudo apt-get purge mongo-tools* and sudo apt-get purge mongodb-mongosh*, and this seemed to fix things and permit an install.

For some reason, the uninstall directions in the documentation (command: sudo apt-get purge mongodb-org*) didn't remove mongo-tools. It may have been something I'd installed from another source previously.

Use the --jsonArray option (see https://docs.mongodb.com/database-tools/mongoexport/#std-option-mongoexport.--jsonArray )

I also had problems installing Mongodb on Fedora 33. These problems occurred when I had the following code in /etc/yum.repos.d/mongodb-org.repo :