at least its solved right? On Thu, Sep 9, 2010 at 8:00 AM, wilson <wilson...@gmail.com> wrote:
> I agree with you. I lost almost an hour looking for how to resolve > this problem. Just here I`ve found the solution. > > On 8 set, 23:22, ALISHER ULUGBEKOV <ulugbe...@gmail.com> wrote: > > I am really disappointed that rails 3.0 have a problem, big issue > > with mysql2. > > I googled and surprised that none of the ruby core developers > > mentioning this problem > > at least telling to people about this issue and solution to this > > problem. > > > > Is there anybody who can tell what is going on? > > Thanks > > -- > 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-t...@googlegroups.com. > To unsubscribe from this group, send email to > rubyonrails-talk+unsubscr...@googlegroups.com<rubyonrails-talk%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/rubyonrails-talk?hl=en. > > -- 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-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
