Rails 3.1

Ruby JRuby
21

On 12 September 2011 12:48, Christian MICHON
[email protected] wrote:

Java::JavaLang::NullPointerException:
from
org.jruby.internal.runtime.methods.DefaultMethod.call(DefaultMethod.java:179)
from script.rails.file(script/rails:6)
from java.lang.Thread.run(Thread.java:679)irb(main):006:0>
migrations again in jruby 1.9 mode ?
Yes I’ve done all in 1.9 mode.
May be a problem in postgresql driver?

22

On Mon, Sep 12, 2011 at 12:51 PM, Mauro [email protected] wrote:

ArgumentError: undefined class/module YAML::Syck::DefaultKey
irb(main):005:0> Shop.count
from
org.jruby.internal.runtime.methods.InterpretedMethod.call(InterpretedMethod.java:190)
from
org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:169)
from
org.jruby.util.ShellLauncher$ScriptThreadProcess.run(ShellLauncher.java:140)
Have you done this on a fresh/empty database ? Did you run the

I’ve no more clue. But I would be interested to understand how you
managed to pass migrations in jruby 1.9 mode…

I would suggest before using the console to use a database gui browser
and check indeed that the tables and keys were properly created…

–
Christian

23

On 12 September 2011 12:55, Christian MICHON
[email protected] wrote:

I would suggest before using the console to use a database gui browser
and check indeed that the tables and keys were properly created…

tables are ok, if they don’t then I think that also Show.all or
Show.find(…) shouldn’t work.

24

On Mon, Sep 12, 2011 at 1:00 PM, Mauro [email protected] wrote:

On 12 September 2011 12:55, Christian MICHON [email protected] wrote:

I would suggest before using the console to use a database gui browser
and check indeed that the tables and keys were properly created…

tables are ok, if they don’t then I think that also Show.all or
Show.find(…) shouldn’t work.

true.

Since I cannot get past migrations on my system (windows xp), I cannot
reproduce your bug.

I can only reproduce it if I mix jruby 1.8 mode db migrations with
jruby 1.9 mode rails console.

I still suggest you try to force jruby jvm in 32bits mode, just to see
it’s not jvm 64 bits related.

If someone can reproduce it in a freshly installed environment, to
confirm that migrations is not a problem, I’m interested.

Good luck Mauro…

–
Christian

25

If you’re having some YAML::Syck errors with Rubygems, could it be
related
to this?

http://blog.rubygems.org/2011/08/31/shaving-the-yaml-yacc.html

The simple solution to the blog post is to gem update --system on your
rubygems, which might fix your bundler errors. Not sure though, but
it’s
worth a shot I guess.

-Nick K.

On Mon, Sep 12, 2011 at 06:13, Christian MICHON