To briefly summarise I''m using the native mysql adapter for ruby and it
all
works fine up to a point (mysql keeps killing of my connections if the app
isn''t
used for 8 hours however that''s another issue entirely).
If I install rubyforapache 1.3.1 then after installing I get the following
error:
NameError (uninitialized constant Mysql):
C:/ruby/lib/ruby/gems/1.8/gems/activesupport-1.1.1/lib/active_support/
dependencies.rb:186:in `const_missing''
C:/ruby/lib/ruby/gems/1.8/gems/activerecord-1.11.1/lib/active_record/
connection_adapters/mysql_adapter.rb:37:in `mysql_connection''
C:/ruby/lib/ruby/gems/1.8/gems/activerecord-1.11.1/lib/active_record/
uery_cache.rb:52:in `send''
C:/ruby/lib/ruby/gems/1.8/gems/activerecord-1.11.1/lib/active_record/
query_cache.rb:52:in `connection=''
C:/ruby/lib/ruby/gems/1.8/gems/activerecord-1.11.1/lib/active_record/
connection_adapters/abstract_adapter.rb:108:in `retrieve_connection''
C:/ruby/lib/ruby/gems/1.8/gems/activerecord-1.11.1/lib/active_record/
base.rb:239:in `connection''
C:/ruby/lib/ruby/gems/1.8/gems/activerecord-1.11.1/lib/active_record/
base.rb:461:in `count_by_sql''
C:/ruby/lib/ruby/gems/1.8/gems/activerecord-1.11.1/lib/active_record/
base.rb:454:in `count''
C:/ruby/lib/ruby/gems/1.8/gems/actionpack-1.9.1/lib/action_controller/
pagination.rb:154:in `count_collection_for_pagination''
C:/ruby/lib/ruby/gems/1.8/gems/actionpack-1.9.1/lib/action_controller/
pagination.rb:171:in `paginator_and_collection_for''
and so on...
Has anyone else seen this error or am I missing something. The mysql.so
installed seems unusable on my setup. I have Mysql 4.1.13 also the mysql gem
won''t install on my system.
Attempting remote installation of ''mysql''
Updating Gem source index for: http://gems.rubyforge.org
Building native extensions. This could take a while...
ERROR: While executing gem ... (RuntimeError)
ERROR: Failed to build gem native extension.
Gem files will remain installed in c:/ruby/lib/ruby/gems/1.8/gems/mysql-2.6 for
inspection.
ruby extconf.rb install mysql -p http://192.168.1.254:8080\nchecking for mysql
_query() in mysqlclient.lib... no
checking for main() in m.lib... yes
checking for mysql_query() in mysqlclient.lib... no
checking for main() in z.lib... no
checking for mysql_query() in mysqlclient.lib... no
checking for main() in socket.lib... no
checking for mysql_query() in mysqlclient.lib... no
checking for main() in nsl.lib... no
checking for mysql_query() in mysqlclient.lib... no
I really have no idea how to get a reliable mysql setup on a windows box.
I found that the mysql.so from the previous version of rubyforapache (1.3) worked. Although it dies quite easily, especially when using Typo. I did manage to get the mysql gem to install once on my build machine (which I haven''t been able to do since!) but it still dies quite easily. I haven''t actually tried building it recently as I switched to using PostgreSQL instead. David. On 8/17/05, GArrow <g.arrowsmith-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> To briefly summarise I''m using the native mysql adapter for ruby and it all > works fine up to a point (mysql keeps killing of my connections if the app isn''t > used for 8 hours however that''s another issue entirely). > > If I install rubyforapache 1.3.1 then after installing I get the following error:<snip>> I really have no idea how to get a reliable mysql setup on a windows box. > > > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >
David Hayward <spidahman@...> writes:> > I found that the mysql.so from the previous version of rubyforapache > (1.3) worked. Although it dies quite easily, especially when using > Typo. I did manage to get the mysql gem to install once on my build > machine (which I haven''t been able to do since!) but it still dies > quite easily. I haven''t actually tried building it recently as I > switched to using PostgreSQL instead. > > David. >I downloaded dema''s mysql.so ( http://dema.ruby.com.br/ ) and ran some simple tests and they failed so that rules that out. I think I''ve tried every other mysql.so I can get my hands on to no avail. I''ve had no joy with the mysql gem either, as has anyone I''ve spoken to. I''m not sure if there is a perfect combination of mysql/mysql.so that will give me some stability. I''m close to giving up and reverting back to the native mysql adapter.