# Mysql native binding gem update issues

**URL:** <https://www.ruby-forum.com/t/mysql-native-binding-gem-update-issues/91861>\
**Category:** Rails\
**Created:** [April 12, 2007, 10:19pm UTC](https://www.ruby-forum.com/t/mysql-native-binding-gem-update-issues/91861 "2007-04-12T22:19:09Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![David\_JSOrman](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/b3f665/32.png) [@David\_JSOrman](https://www.ruby-forum.com/u/David_JSOrman)\
**Post date:** [April 12, 2007, 10:19pm UTC](https://www.ruby-forum.com/t/mysql-native-binding-gem-update-issues/91861/1 "2007-04-12T22:19:09Z")

</div>

A couple questions concerning the native mysql binding gem.

#1 - Why does it not search PATH for mysql\_config so I don’t have to  
keep specifying it on the command line?

#2 - Why does it always prompt me to reinstall when I do “gem update”?

I’ve seen #2 asked a lot on various pages (Thanks, Google…) - but  
I’ve seen no answers. Is there a planned update to address this issue?  
As to #1 - I think this is a “no brainer” type of fix, and it would  
solve a lot of problems for a lot of users, again judging from various  
posts found via Google when researching the problem myself.

I appreciate any input you can give me, even if it’s telling me who to  
contact. 🙂

Cheers,  
David