From 147fc39b8c61a625dd0ac8fe2ff0d588951ca4b0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Mikael=20St=C3=A5ldal?= <mst@appearnetworks.com>
Date: Fri, 5 Dec 2014 11:31:37 +0100
Subject: [PATCH] Document supporting ByteBuffer and ByteBuf as parameters in
 prepared statements

---
 mysql-async/README.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/mysql-async/README.md b/mysql-async/README.md
index 207d60d1..adff299e 100644
--- a/mysql-async/README.md
+++ b/mysql-async/README.md
@@ -89,6 +89,8 @@ java.sql.Timestamp | timestamp
 java.sql.Time | time
 String | string
 Array[Byte] | blob
+java.nio.ByteBuffer | blob
+io.netty.buffer.ByteBuf | blob
 
 You don't have to match exact values when sending parameters for your prepared statements, MySQL is usually smart
 enough to understand that if you have sent an Int to `smallint` column it has to truncate the 4 bytes into 2.