JRUBY-2404/1638 Table name parse error not fixed in 1.1.2?

Ruby JRuby
1

This bug was apparently fixed
(http://jira.codehaus.org/browse/JRUBY-2404),
but according to the list at http://wiki.jruby.org/wiki/JRuby_1.1.2 did
not
make it into this release. Just tried 1.1.2 out, and I am getting the
same
behaviour as before. Bit of a shame, as this was one of the bugs that
was
specifically highlighted in the pre 1.1.2 discussion. Hope it is my
user
error.

Richard F.

View this message in context:
http://www.nabble.com/JRUBY-2404-1638-Table-name-parse-error-not-fixed-in-1.1.2--tp17571955p17571955.html
Sent from the JRuby - User mailing list archive at Nabble.com.

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email
2

Are you sure that this belongs in JRuby main project? It seems like a
fix for
the ActiveRecord-JDBC component, which is released separately from
JRuby. I
don’t think Nick has cut the post 0.8 release yet.

Peter

3

Peter K Chan wrote:

Are you sure that this belongs in JRuby main project? It seems like a fix
for
the ActiveRecord-JDBC component, which is released separately from JRuby.
I
don’t think Nick has cut the post 0.8 release yet.

Peter

You could be right, but the impression I got from the thread 'JRuby
1.1.2

Richard F.

View this message in context:
http://www.nabble.com/JRUBY-2404-1638-Table-name-parse-error-not-fixed-in-1.1.2--tp17571955p17573321.html
Sent from the JRuby - User mailing list archive at Nabble.com.

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email
4

Hi Richard,

On Sat, May 31, 2008 at 11:01 AM, Richard F. [email protected]
wrote:

You could be right, but the impression I got from the thread 'JRuby 1.1.2

My understanding of the process is that first JRuby is being released.
And short after, new versions of important JRuby-specific gems like
ActiveRecord-JDBC, Warbler, etc, will/could follow.

Activerecord-JDBC is in separate repository and I know of no plans to
merge it right into JRuby (there is no need for that, I’d think). I
see in that repository that the bug you’re referring to has been fixed
indeed, and will appear in the next version.

Given that currently many JRuby-core folks are at RailsConf, it would
take a few days.

Thanks,
–Vladimir

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email