# How to tell if MySQL native bindings are used (Win32)?

**URL:** <https://www.ruby-forum.com/t/how-to-tell-if-mysql-native-bindings-are-used-win32/140211>\
**Category:** Rails\
**Created:** [June 11, 2008, 10:30pm UTC](https://www.ruby-forum.com/t/how-to-tell-if-mysql-native-bindings-are-used-win32/140211 "2008-06-11T22:30:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kuma](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/a587f6/32.png) [@kuma](https://www.ruby-forum.com/u/kuma)\
**Post date:** [June 11, 2008, 10:30pm UTC](https://www.ruby-forum.com/t/how-to-tell-if-mysql-native-bindings-are-used-win32/140211/1 "2008-06-11T22:30:57Z")

</div>

Hi all,

I believe I’ve installed the Windows native© bindings for MySQL by  
executing ‘gem install mysql’ and choosing the ‘1. mysql 2.7.3  
(mswin32)’ option. However, I’m not sure how to tell if Rails is making  
use of this.

I am able to execute “require ‘mysql.so’” in irb, so I think the C  
bindings are installed properly. However, I expected to see a  
difference in performance for my fixture load and I did not. Is there a  
definitive way I can tell if these bindings are being used?

Thanks!

Brian H.

---

<div class="post-metadata">

**Author:** ![kuma](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/a587f6/32.png) [@kuma](https://www.ruby-forum.com/u/kuma)\
**Post date:** [June 11, 2008, 10:44pm UTC](https://www.ruby-forum.com/t/how-to-tell-if-mysql-native-bindings-are-used-win32/140211/2 "2008-06-11T22:44:00Z")

</div>

On 11 Jun 2008, at 21:30, Brian H. wrote:

> bindings are installed properly. However, I expected to see a  
> difference in performance for my fixture load and I did not. Is  
> there a  
> definitive way I can tell if these bindings are being used?

rails prints a warning message when it uses the pure ruby ones. If you  
wanted to be really sure I suppose you could just remove the ruby one  
(activerecord/lib/active\_record/vendor/mysql.rb). I think performance  
differences would be more noticeable when returning large result sets.

Fred