Skip to content

1.9.0 - Fix which set of column info is used for binary resultset decoding

Latest

Choose a tag to compare

@penny-for-vapor penny-for-vapor released this 23 Dec 15:48
e62e6aa

What's Changed

Fix which set of column info is used for binary resultset decoding by @gwynne in #117

This solves the driver crashing when executing a query which returns columns whose COM_STMT_EXECUTE response column info is different from the COM_STMT_PREPARE_OK column info. In practice this happens for result fields which are expressions whose type differs from that of the underlying columns, e.g.. SELECT (foo = 1) AS is_one FROM bar;—the prepare column info will claim is_one is a BIGINT, but the execute column info will show it to be an INTEGER, which has a different (smaller) binary encoding.

Also bumps the package to Swift 6.

Closes #115.

Reviewers

Thanks to the reviewers for their help:

This patch was released by @gwynne

Full Changelog: 1.8.0...1.9.0