Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

Sorry, you do not have permission to ask a question, You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please type your username.

Please type your E-Mail.

Please choose an appropriate title for the post.

Please choose the appropriate section so your post can be easily searched.

Please choose suitable Keywords Ex: post, video.

Browse

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

Querify Question Shop: Explore Expert Solutions and Unique Q&A Merchandise

Querify Question Shop: Explore Expert Solutions and Unique Q&A Merchandise Logo Querify Question Shop: Explore Expert Solutions and Unique Q&A Merchandise Logo

Querify Question Shop: Explore Expert Solutions and Unique Q&A Merchandise Navigation

  • Home
  • About Us
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • About Us
  • Contact Us
Home/ Questions/Q 3337

Querify Question Shop: Explore Expert Solutions and Unique Q&A Merchandise Latest Questions

Author
  • 61k
Author
Asked: November 26, 20242024-11-26T01:47:11+00:00 2024-11-26T01:47:11+00:00

Custom ordering without custom SQL with Ruby on Rails 7

  • 61k

Custom order SQL

The problem
It's a common case for Rails applications to have enum fields on a model like:

class Review < ApplicationRecord   enum status: [:pending, :processing, :completed] end 
Enter fullscreen mode Exit fullscreen mode

All's good until we need to sort records by their status in a specific order. For example, on reviews page records should be ordered by status in alphabetical order, but internally in DB status values are stored as integers.
We can't just add order(status: :asc). Previously we'd have to write some custom SQL for the task:

Review.order("   CASE status   WHEN 2 THEN 1   WHEN 0 THEN 2   WHEN 1 THEN 3   END   ASC ") 
Enter fullscreen mode Exit fullscreen mode

The solution
Ruby on Rails 7.0 provides a new query method #in_order_of which accepts as arguments a column name and an array of values in order we want the records to be ordered by:

Review.in_order_of(   :status, [:complete, :pending, :processing] ) 
Enter fullscreen mode Exit fullscreen mode

Which translates to SQL query like:

SELECT "reviews".* FROM "reviews"  WHERE "reviews"."status" IN (2, 0, 1)  ORDER BY CASE "reviews"."status"   WHEN 2 THEN 1    WHEN 0 THEN 2    WHEN 1 THEN 3  END ASC 
Enter fullscreen mode Exit fullscreen mode

This works well, as long as we don't have/care about reviews with NULL as their status.
If we try to pass nil to the values array:

Review.in_order_of(   :status, [nil, :complete, :pending, :processing] ) 
Enter fullscreen mode Exit fullscreen mode

Following SQL would be created:

SELECT "reviews".* FROM "reviews"  WHERE "reviews"."status" IN (NULL, 2, 0, 1)  ORDER BY CASE "reviews"."status"   WHEN NULL THEN 1   WHEN 2 THEN 2   WHEN 0 THEN 3   WHEN 1 THEN 4 END ASC 
Enter fullscreen mode Exit fullscreen mode

But since NULL in SQL is a special value and NULL != NULL, then this query simply won't return records with NULL as a status at all.

The improvement
Ruby on Rails 7.0.7 further improves the method: now it correctly handles the NULL values, so the resulting query would be:

SELECT "reviews".* FROM "reviews"  WHERE (   "reviews"."status" IN (2, 0, 1)   OR "reviews"."status" IS NULL ) ORDER BY CASE    WHEN "reviews"."status" IS NULL THEN 1   WHEN "reviews"."status" = 2 THEN 2   WHEN "reviews"."status" = 0 THEN 3   WHEN "reviews"."status" = 1 THEN 4 END ASC 
Enter fullscreen mode Exit fullscreen mode

Now it does exactly what we need without writing any custom SQL queries.

railsrubysqlwebdev
  • 0 0 Answers
  • 1 View
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

Sidebar

Ask A Question

Stats

  • Questions 4k
  • Answers 0
  • Best Answers 0
  • Users 2k
  • Popular
  • Answers
  • Author

    ES6 - A beginners guide - Template Literals

    • 0 Answers
  • Author

    Understanding Higher Order Functions in JavaScript.

    • 0 Answers
  • Author

    Build a custom video chat app with Daily and Vue.js

    • 0 Answers

Top Members

Samantha Carter

Samantha Carter

  • 0 Questions
  • 20 Points
Begginer
Ella Lewis

Ella Lewis

  • 0 Questions
  • 20 Points
Begginer
Isaac Anderson

Isaac Anderson

  • 0 Questions
  • 20 Points
Begginer

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help

Footer

Querify Question Shop: Explore Expert Solutions and Unique Q&A Merchandise

Querify Question Shop: Explore, ask, and connect. Join our vibrant Q&A community today!

About Us

  • About Us
  • Contact Us
  • All Users

Legal Stuff

  • Terms of Use
  • Privacy Policy
  • Cookie Policy

Help

  • Knowledge Base
  • Support

Follow

© 2022 Querify Question. All Rights Reserved

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.