BASH "open wait until file SP_QUERY_RESULT_STATUS_FILE was written to disk call sequelpro:// URL scheme command (via e.g.write the to be passed data into the file SP_QUERY_FILE.remove files SP_QUERY_RESULT_FILE, SP_QUERY_RESULT_STATUS_FILE (optionally SP_QUERY_FILE, SP_QUERY_RESULT_META_FILE).
#Schema sequel pro pro
The following describes the general workflow to pass data to Sequel Pro and to get possible returned data from Sequel Pro if a command not works with parameters only.
Since these commands are URLs one has to escape parameters according to RFC 1808 specification. Some uncritical URL scheme commands can be used without a passed SP_PROCESS_ID, then these commands will send to the front most connection window.Īll data in used commands are UTF-8 encoded. A Bundle command generates randomly during invocation an Universally Unified Identification (UUID) string which will be passed as shell variable SP_PROCESS_ID and has to be used as authentication string and links a Bundle command to the connection window from which the Bundle command was called. These URL scheme commands are only available from inside a Bundle command including the HTML output window. In order to prevent misusage of these URL scheme commands an authentication is used. A URL scheme command can send actins to Sequel Pro but also return data which is realised by a file hand-shake mechanism. BASH command open sequel://… which also be used in the built-in JavaScript object system method run() of the HTML output window. Sequel Pro listens at a URL scheme sequelpro:// which can be used as hyperlink in the HTML output window or in any Bundle command script via the e.g.
0 kommentar(er)
