Forum: Ruby on Rails Help with MySQL COALESCE

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
tni (Guest)
on 2009-05-11 22:38
(Received via mailing list)
In my Ruby on Rails app, I am trying to run a query to populate a drop-
down select box.  The query may return NULL values, in which case I
want to display a value like 'N/A'.
My query works directly in MySql:
select distinct(coalesce(time, "N/A")) from mytable;

But when I run this in the app using mytable.find(),
the null value is returned as a 0.  The database column is an integer.
Is Ruby somehow changing my desired value to 0 because it's an
integer??
Again, I get the desired results in MySql.

In Ruby on Rails, how can I replace the NULL value with some text
value that will make more sense to
the user?
Andrew T. (Guest)
on 2009-05-12 06:53
(Received via mailing list)
On Mon, May 11, 2009 at 7:02 PM, tni <removed_email_address@domain.invalid> 
wrote:
> integer??
> Again, I get the desired results in MySql.
>
> In Ruby on Rails, how can I replace the NULL value with some text
> value that will make more sense to
> the user?

Yes, Rails is changing the value to an int because of the db schema.
Rails will return nil if the field is null so why don't you just do
the 'COALESCE' in rails

<%= my_table.time || 'N/A' %>

Andrew T.
http://ramblingsonrails.com
http://www.linkedin.com/in/andrewtimberlake

"I have never let my schooling interfere with my education" - Mark Twain
tni (Guest)
on 2009-05-12 17:55
(Received via mailing list)
I am not specifically setting that field in the view as you suggested,
which was a good idea.
I am using the collection returned by running the find to feed a
filter function which is defining the filter fields being used
to build queries.  I really needed to have the collection contain the
appropriate data before being passed into the
filter code....

On May 11, 10:52 pm, Andrew T. <removed_email_address@domain.invalid>
This topic is locked and can not be replied to.