npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@runnerty/executor-mysql

v3.2.1

Published

Runnerty module: MySQL executor

Downloads

105

Readme

NPM version Downloads

MySQL executor for Runnerty:

Installation:

Through NPM

npm i @runnerty/executor-mysql

You can also add modules to your project with runnerty

npx runnerty add @runnerty/executor-mysql

This command installs the module in your project, adds example configuration in your config.json and creates an example plan of use.

If you have installed runnerty globally you can include the module with this command:

runnerty add @runnerty/executor-mysql

Configuration:

Add in config.json:

{
  "id": "mysql_default",
  "type": "@runnerty-executor-mysql",
  "user": "mysqlusr",
  "password": "mysqlpass",
  "database": "MYDB",
  "host": "myhost.com",
  "port": "3306"
}
{
  "id": "mysql_default",
  "type": "@runnerty-executor-mysql",
  "user": "mysqlusr",
  "password": "mysqlpass",
  "database": "MYDB",
  "host": "myhost.com",
  "port": "3306",
  "ssl": {
    "ca": "./ssl/my.ca"
  }
}

Configuration params:

| Parameter | Description | | :----------------- | :---------------------------------------------------------------------------------------------------------- | | user | The MySQL user to authenticate as. | | password | The password of that MySQL user. | | database | Name of the database to use for this connection. (Optional) | | host | The hostname of the database you are connecting to. | | port | The port number to connect to. (Default: 3306) | | socketPath | The path to a unix domain socket to connect to. When used host and port are ignored. (Optional) | | charset | The charset for the connection (collation). (Default: 'UTF8_GENERAL_CI') | | timezone | The timezone configured on the MySQL server. (Default: 'local') | | insecureAuth | Allow connecting to MySQL instances that ask for the old (insecure) authentication method. (Default: false) | | flags | Connection flags. More information here. | | multipleStatements | Allow multiple mysql statements per query. (Default: true) | | ssl/ca | SSL CA File (Optional) | | ssl/cert | SSL CERT File (Optional) | | ssl/key | SSL KEY File (Optional) |

Plan sample:

Add in plan.json:

{
  "id": "mysql_default",
  "command_file": "/etc/runnerty/sql/test.sql"
}
{
  "id": "mysql_default",
  "command": "SELECT NOW()"
}

Generation of files:

The saved can be indicated in the file of the results obtained from a query in csv, xlsx and json format. These files will be generated with streams. You only have to indicate the corresponding property in the parameters:

XLSX

XLSX Format

| Parameter | Description | | :------------- | :---------------------------- | | xlsxFileExport | Path of xlsx file export. | | xlsxAuthorName | Author file name. (Optional) | | xlsxSheetName | Name of the sheet. (Optional) |

Sample:

{
  "id": "mysql_sample",
  "command": "SELECT * FROM USERS",
  "xlsxFileExport": "./my_output.xlsx",
  "xlsxAuthorName": "Runnerty",
  "xlsxSheetName": "MySheetSample"
}

CSV

CSV Format

| Parameter | Description | | :-------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | csvFileExport | Path of csv file export. | | csvOptions/headers | Type: boolean/string[]. The headers will be auto detected from the first row or you can to provide headers array: ['h1name','h2name',...]. | | csvOptions/delimiter | Alternate delimiter. (Default: ',') | | csvOptions/quote | Alternate quote. (Default: '"') | | csvOptions/alwaysWriteHeaders | Set to true if you always want headers written, even if no rows are written. (Default: false) | | csvOptions/rowDelimiter | Specify an alternate row delimiter (i.e \r\n). (Default: '\n') | | csvOptions/quoteHeaders | If true then all headers will be quoted. (Default: quoteColumns value) | | csvOptions/quoteColumns | If true then columns and headers will be quoted (unless quoteHeaders is specified). (Default: false). More info here. | | csvOptions/escape | Alternate escaping value. (Default: '"') | | csvOptions/includeEndRowDelimiter | Set to true to include a row delimiter at the end of the csv. (Default: false) | | csvOptions/writeBOM | Set to true if you want the first character written to the stream to be a utf-8 BOM character. (Default: false) |

Sample:

{
  "id": "mysql_sample",
  "command": "SELECT * FROM USERS",
  "csvFileExport": "@GV(WORK_DIR)/users.csv",
  "csvOptions": {
    "delimiter": ";",
    "quote": "\""
  }
}

JSON

JSON Format

Sample:

{
  "id": "mysql_sample",
  "command": "SELECT * FROM USERS",
  "fileExport": "@GV(WORK_DIR)/users.json"
}

Loading files:

For file upload you must indicate the path of the file to be loaded in the localInFile parameter and in the LOAD DATA LOCAL INFILE statement you must indicate mystream. For example:

  • localInFile: Plain file path
{
  "id": "mysql_sample",
  "command": "LOAD DATA LOCAL INFILE 'mystream' INTO TABLE DBSAMPLE.TABLESAMPLE FIELDS TERMINATED BY ',' LINES TERMINATED BY '\n'",
  "localInFile": "/sample.csv"
}

Output (Process values):

Standard

  • PROCESS_EXEC_MSG_OUTPUT: MySQL output message.
  • PROCESS_EXEC_ERR_OUTPUT: Error output message.

Query output

  • PROCESS_EXEC_DATA_OUTPUT: MySQL query output data.
  • PROCESS_EXEC_DB_COUNTROWS: MySQL query count rows.
  • PROCESS_EXEC_DB_FIRSTROW: MySQL query first row data.
  • PROCESS_EXEC_DB_FIRSTROW_[FILED_NAME]: MySQL first row field data.

Operation output

  • PROCESS_EXEC_DB_FIELDCOUNT: MySQL field count.
  • PROCESS_EXEC_DB_AFFECTEDROWS: MySQL affected rows count.
  • PROCESS_EXEC_DB_CHANGEDROWS: MySQL changed rows count.
  • PROCESS_EXEC_DB_INSERTID: MySQL insert ID.
  • PROCESS_EXEC_DB_WARNINGCOUNT: MySQL warning count.
  • PROCESS_EXEC_DB_MESSAGE: MySQL message.