Via mql(1) as a daemon

Overview

Setting up the mql(1) program as a daemon has much the same benefits and drawbacks as using it as a command.

Additional benefits include:

Persistence of connection: You can keep the connection (and thus the mql(1) program) running for as long as you like, thus eliminating the performance-problems relating to starting and stopping the mql(1) process and the back-end connection.
It may be simpler to connect via a TCP/IP socket than via an external program if you use a scripting language.
You can connect remotely, and from architectures that do not have the mql(1) program.

Drawbacks include:

There may be security-related problems with having an mql daemon running on your system.
Emdros is fundamentally a single-user system. If more than one mql(1) process is spawned at a time, your mileage may vary.

However, the single-user status only applies to MQL statements that create or update or delete data, not to querying. If your database is in a phase in which it is not created/updated/deleted, but only queried, then you should be able to run mql(1) as a daemon with no problems.