JRuby

Custom selected fields in ActiveRecord queries are returned as strings

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Minor Minor
  • Resolution: Incomplete
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: Miscellaneous
  • Labels:
    None
  • Environment:
    Rails 3.0.7, JRuby 1.6.4, MySQL
  • Number of attachments :
    2

Description

Custom selected fields are returned as strings in JRuby, while in MRI are converted to appropriate class.
Here is a very simple example. Having User model with created_at datetime field MRI returns Time object:

ruby-1.8.7-p330 :001 > User.select('created_at AS custom_created_at').first.custom_created_at.class
=> Time

while JRuby returns string:

jruby-1.6.4 :029 > User.select('created_at AS custom_created_at').first.custom_created_at.class
=> String

The same problem is with other field types.

  1. File
    jruby_custom_select_bug_final.rb
    16/Nov/11 2:59 PM
    1 kB
    Michal Ochman
  2. File
    jruby_custom_select_bug.rb
    16/Nov/11 2:47 PM
    1 kB
    Michal Ochman

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Charles Oliver Nutter added a comment -

You might get a quicker response filing this at the AR-JDBC JIRA (http://kenai.com/jira/browse/ACTIVERECORD_JDBC) or at the Github isssues (https://github.com/jruby/activerecord-jdbc-adapter/issues).

To clarify...the created_at field in the database is of type DATETIME and we're returning it as a string, yes? Is it possible for you to create a simple script that demonstrates the problem, so we know exactly how to reproduce?

Show
Charles Oliver Nutter added a comment - You might get a quicker response filing this at the AR-JDBC JIRA ( http://kenai.com/jira/browse/ACTIVERECORD_JDBC ) or at the Github isssues ( https://github.com/jruby/activerecord-jdbc-adapter/issues ). To clarify...the created_at field in the database is of type DATETIME and we're returning it as a string, yes? Is it possible for you to create a simple script that demonstrates the problem, so we know exactly how to reproduce?
Hide
Permalink
Michal Ochman added a comment -

Test file. Please remember to update DB configuration options.

Show
Michal Ochman added a comment - Test file. Please remember to update DB configuration options.
Hide
Permalink
Michal Ochman added a comment -

I'm not able to remove older file I uploaded, so please ignore it and take a look at jruby_custom_select_bug_final.rb.
Assertions in files shows where is the problem. As you can see regular queries work just fine, but custom select statements don't behave in the same way as the ones run with mysql2 gem.

Show
Michal Ochman added a comment - I'm not able to remove older file I uploaded, so please ignore it and take a look at jruby_custom_select_bug_final.rb. Assertions in files shows where is the problem. As you can see regular queries work just fine, but custom select statements don't behave in the same way as the ones run with mysql2 gem.
Hide
Permalink
Charles Oliver Nutter added a comment -

Is this bug still valid? Have you tried filing it against AR-JDBC proper? Like I mentioned, AR-JDBC bugs here don't get as much attention

Show
Charles Oliver Nutter added a comment - Is this bug still valid? Have you tried filing it against AR-JDBC proper? Like I mentioned, AR-JDBC bugs here don't get as much attention
Hide
Permalink
Charles Oliver Nutter added a comment -

No follow-up in a while, and this should be filed with AR-JDBC anyway.

Show
Charles Oliver Nutter added a comment - No follow-up in a while, and this should be filed with AR-JDBC anyway.

People

  • Assignee:
    Charles Oliver Nutter
    Reporter:
    Michal Ochman
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: