Running Instant Rails - latest version. When I run rake db:migrate, I get the error (in a pop up window): The procedure entry point mysql_stmt_row_tell could not be located in the dynamic link library LIBMYSQL.dll. After clicking ok several times the migration runs. My site also runs locally. What''s this error all about? Thanks. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
I realized the problem started happening after I install the mysql gem, based on advice from ''Agile Web Development With Rails'' page 292. So I uninstalled that gem and the error went away. The reason I installed it is because DHH recommended it to increase performance. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
On 3/27/07, Will Merydith <rails-mailing-list-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org> wrote:> > I realized the problem started happening after I install the mysql gem, > based on advice from ''Agile Web Development With Rails'' page 292. So I > uninstalled that gem and the error went away. > > The reason I installed it is because DHH recommended it to increase > performance.Actually, you don''t need to install it as it is already included in Instant Rails. Curt --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
I received the same error message. After copying libmysql.dll (from my MySQL installation) to my ruby/bin folder, the error went away. I''m not sure if there are any potentially negative consequences of copying the file, but everything seems to be working for now. Will Merydith wrote:> Running Instant Rails - latest version. > > When I run rake db:migrate, I get the error (in a pop up window): > > The procedure entry point mysql_stmt_row_tell could not be located in > the dynamic link library LIBMYSQL.dll. > > After clicking ok several times the migration runs. My site also runs > locally. > > What''s this error all about? > > Thanks.-- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Samuel Johnson wrote:> I received the same error message. After copying libmysql.dll (from my > MySQL installation) to my ruby/bin folder, the error went away. I''m not > sure if there are any potentially negative consequences of copying the > file, but everything seems to be working for now. > >It really does resolve the problem. Thanks. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
this works as mentioned above: copy libmysql.dll (from my MySQL installation) to my ruby/bin folder -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.