Swiftpack.co -  Package - vapor/mysql-nio
Swiftpack.co is a collection of thousands of indexed Swift packages. Search packages.
vapor/mysql-nio
🐬 Non-blocking, event-driven Swift client for MySQL.
.package(url: "https://github.com/vapor/mysql-nio.git", from: "1.3.2")
MySQLNIO Documentation Team Chat MIT License CI Swift 5.2

🐬 Non-blocking, event-driven Swift client for MySQL built on SwiftNIO.

Major Releases

The table below shows a list of PostgresNIO major releases alongside their compatible NIO and Swift versions.

Version NIO Swift SPM
1.0 2.0+ 5.2+ from: "1.0.0"

Use the SPM string to easily include the dependendency in your Package.swift file.

.package(url: "https://github.com/vapor/mysql-nio.git", from: ...)

Supported Platforms

MySQLNIO supports the following platforms:

  • Ubuntu 16.04, 18.04, 20.04
  • macOS 10.15, 11
  • CentOS 8
  • Amazon Linux 2

Overview

MySQLNIO is a client package for connecting to, authorizing, and querying a MySQL server. At the heart of this module are NIO channel handlers for parsing and serializing messages in MySQL's proprietary wire protocol. These channel handlers are combined in a request / response style connection type that provides a convenient, client-like interface for performing queries.

Support for both simple (text) and parameterized (prepared statement) querying is provided out of the box alongside a MySQLData type that handles conversion between MySQL's wire format and native Swift types.

Motivation

Most Swift implementations of MySQL clients are based on the libmysqlclient C library which handles transport internally. Building a library directly on top of MySQL's wire protocol using SwiftNIO should yield a more reliable, maintainable, and performant interface for MySQL databases.

Goals

This package is meant to be a low-level, unopinionated MySQL wire-protocol implementation for Swift. The hope is that higher level packages can share MySQLNIO as a foundation for interacting with MySQL servers without needing to duplicate complex logic.

Because of this, MySQLNIO excludes some important concepts for the sake of simplicity, such as:

  • Connection pooling
  • Swift Codable integration
  • Query building

If you are looking for a MySQL client package to use in your project, take a look at these higher-level packages built on top of MySQLNIO:

Dependencies

This package has four dependencies:

This package has no additional system dependencies.

API Docs

Check out the MySQLNIO API docs for a detailed look at all of the classes, structs, protocols, and more.

Getting Started

This section will provide a quick look at using MySQLNIO.

Creating a Connection

The first step to making a query is creating a new MySQLConnection. The minimum requirements to create one are a SocketAddress, EventLoop, and credentials.

import MySQLNIO

let eventLoop: EventLoop = ...
let conn = try MySQLConnection(
    to: .makeAddressResolvingHost("my.mysql.server", port: 5432),
    username: "vapor_username",
    database: "vapor_database",
    password: "vapor_password",
    on: eventLoop
).wait()

Note: These examples will make use of wait() for simplicity. This is appropriate if you are using MySQLNIO on the main thread, like for a CLI tool or in tests. However, you should never use wait() on an event loop.

There are a few ways to create a SocketAddress:

  • init(ipAddress: String, port: Int)
  • init(unixDomainSocketPath: String)
  • makeAddressResolvingHost(_ host: String, port: Int)

There are also some additional arguments you can supply to connect.

  • tlsConfiguration An optional TLSConfiguration struct. This will be used if the MySQL server supports TLS. Pass nil to opt-out of TLS.
  • serverHostname An optional String to use in conjunction with tlsConfiguration to specify the server's hostname.

connect will return a future MySQLConnection, or an error if it could not connect.

Database Protocol

Interaction with a server revolves around the MySQLDatabase protocol. This protocol includes methods like query(_:) for executing SQL queries and reading the resulting rows.

MySQLConnection is the default implementation of MySQLDatabase provided by this package. Assume the client here is the connection from the previous example.

import MySQLNIO

let db: MySQLDatabase = ...
// now we can use client to do queries

Simple Query

Simple (text) queries allow you to execute a SQL string on the connected MySQL server. These queries do not support binding parameters, so any values sent must be escaped manually.

These queries are most useful for schema or transactional queries, or simple selects. Note that values returned by simple queries will be transferred in the less efficient text format.

simpleQuery has two overloads, one that returns an array of rows, and one that accepts a closure for handling each row as it is returned.

let rows = try db.simpleQuery("SELECT @@version").wait()
print(rows) // [["@@version": "8.x.x"]]

try db.simpleQuery("SELECT @@version") { row in
    print(row) // ["@@version": "8.x.x"]
}.wait()

Parameterized Query

Parameterized (prepared statement) queries allow you to execute a SQL string on the connected MySQL server. These queries support passing bound parameters as a separate argument. Each parameter is represented in the SQL string using placeholders (?).

These queries are most useful for selecting, inserting, and updating data. Data for these queries is transferred using the highly efficient binary format.

Just like simpleQuery, query also offers two overloads. One that returns an array of rows, and one that accepts a closure for handling each row as it is returned.

let rows = try db.query("SELECT * FROM planets WHERE name = ?", ["Earth"]).wait()
print(rows) // [["id": 42, "name": "Earth"]]

try db.query("SELECT * FROM planets WHERE name = ?", ["Earth"]) { row in
    print(row) // ["id": 42, "name": "Earth"]
}.wait()

Rows and Data

Both simpleQuery and query return the same MySQLRow type. Columns can be fetched from the row using the column(_:table:) method.

let row: MySQLRow = ...
let version = row.column("name")
print(version) // MySQLData?

MySQLRow columns are stored as MySQLData. This struct contains the raw bytes returned by MySQL as well as some information for parsing them, such as:

  • MySQL data type
  • Wire format: binary or text
  • Value as array of bytes

MySQLData has a variety of convenience methods for converting column data to usable Swift types.

let data: MySQLData = ...

print(data.string) // String?

print(data.int) // Int?
print(data.int8) // Int8?
print(data.int16) // Int16?
print(data.int32) // Int32?
print(data.int64) // Int64?

print(data.uint) // UInt?
print(data.uint8) // UInt8?
print(data.uint16) // UInt16?
print(data.uint32) // UInt32?
print(data.uint64) // UInt64?

print(data.bool) // Bool?

try print(data.json(as: Foo.self)) // Foo?

print(data.float) // Float?
print(data.double) // Double?

print(data.date) // Date?
print(data.uuid) // UUID?
print(data.decimal) // Decimal?

print(data.time) // MySQLTime?

MySQLData is also used for sending data to the server via parameterized values. To create MySQLData from a Swift type, use the available intializer methods.

GitHub

link
Stars: 24
Last commit: 4 weeks ago

Release Notes

Fix handling of null columns in TextResultSetRow
26 weeks ago
This patch was authored by @NobodyNada and released by @tanner0101.

When TextResultSetRow encountered a null column, it did not increment the buffer index, and so it would repeatedly read NULL into every remaining column. This patch fixes the issue and adds regression tests (#57).

Swiftpack is being maintained by Petr Pavlik | @ptrpavlik | @swiftpackco