I installed new ruby 1.7.2 (2002-08-21) from cvs and get warning in
httpd.log:
/usr/local/lib/ruby/1.7/auto-reload.rb:53: warning: no super class
for SQL::Error', Object assumed /usr/local/lib/ruby/1.7/auto-reload.rb:53: warning: no super class forSQL::PGConn’, Object assumed
…
/…/mylib.rb:33:in connect': undefined method(null)’ for
#SQL::PGConn:0x8360d64 (NoMethodError)
SQL::Error defined in c extension:
rb_mSQL = rb_define_module(“SQL”);
rb_eError = rb_define_class_under(rb_mSQL, “Error”, rb_eRuntimeError);
rb_cPG = rb_define_class_under(rb_mSQL, “PGConn”, rb_cObject);
…
What is happening? It has worked before and now fails.
/usr/local/lib/ruby/1.7/auto-reload.rb:53: warning: no super class
for `SQL::Error', Object assumed
/usr/local/lib/ruby/1.7/auto-reload.rb:53: warning: no super class
for `SQL::PGConn', Object assumed
Have you stopped and restarted your server after the installation of
the new version of ruby ?
I installed new ruby 1.7.2 (2002-08-21) from cvs and get warning in
httpd.log:
/usr/local/lib/ruby/1.7/auto-reload.rb:53: warning: no super class
for SQL::Error', Object assumed /usr/local/lib/ruby/1.7/auto-reload.rb:53: warning: no super class for SQL::PGConn’, Object assumed
…
/…/mylib.rb:33:in connect': undefined method (null)’ for
#SQL::PGConn:0x8360d64 (NoMethodError)
SQL::Error defined in c extension:
rb_mSQL = rb_define_module(“SQL”);
rb_eError = rb_define_class_under(rb_mSQL, “Error”, rb_eRuntimeError);
rb_cPG = rb_define_class_under(rb_mSQL, “PGConn”, rb_cObject);
…
What is happening? It has worked before and now fails.
just a guess… mybe you should recompile pgsql-ruby?
I installed new ruby 1.7.2 (2002-08-21) from cvs and get warning in
httpd.log:
/usr/local/lib/ruby/1.7/auto-reload.rb:53: warning: no super class
for SQL::Error', Object assumed /usr/local/lib/ruby/1.7/auto-reload.rb:53: warning: no super class for SQL::PGConn’, Object assumed
…
/…/mylib.rb:33:in connect': undefined method (null)’ for
#SQL::PGConn:0x8360d64 (NoMethodError)
SQL::Error defined in c extension:
rb_mSQL = rb_define_module(“SQL”);
rb_eError = rb_define_class_under(rb_mSQL, “Error”, rb_eRuntimeError);
rb_cPG = rb_define_class_under(rb_mSQL, “PGConn”, rb_cObject);
…
What is happening? It has worked before and now fails.
I’ve been tracking the latest cvs and there has been at
least one bug that would make ruby unusable in the last
couple weeks. The cvs version is development and you need
to test it before using it. I would definitely run rubicon
against it before installing.
/usr/local/lib/ruby/1.7/auto-reload.rb:53: warning: no super class
for SQL::Error', Object assumed /usr/local/lib/ruby/1.7/auto-reload.rb:53: warning: no super class for SQL::PGConn’, Object assumed
Have you stopped and restarted your server after the installation of
the new version of ruby ?
I don’t understand what happens - the same configuration on another
computer works fine without warnings and errors. Web applications are
difficult to debug, I can’t reproduce this behavior in plain script. I
asked help in hope that somebody had meet the same problem.
Don’t bother, I installed June version - it works fine.
I’ve been tracking the latest cvs and there has been at
least one bug that would make ruby unusable in the last
couple weeks. The cvs version is development and you need
to test it before using it. I would definitely run rubicon
against it before installing.
Don’t forget to tell what the bug is. I’d be glad to fix.
I’ve been tracking the latest cvs and there has been at
least one bug that would make ruby unusable in the last
couple weeks. The cvs version is development and you need
to test it before using it. I would definitely run rubicon
against it before installing.
Don’t forget to tell what the bug is. I’d be glad to fix.
Already Done. Submitting to ruby-bugs is the First thing
I do.