This project is archived and is in readonly mode.

#2926 ✓stale
Steve

Passing :distinct => true causes an error

Reported by Steve | July 20th, 2009 @ 06:18 PM | in 3.x

Shouldn't named scopes be able to specify distinct? Although I could say select => 'DISTINCT tablename.*' for a find this doesn't work for a count?

Comments and changes to this ticket

  • Jeremy Kemper

    Jeremy Kemper May 4th, 2010 @ 06:48 PM

    • Milestone changed from 2.x to 3.x
  • Dan Pickett

    Dan Pickett May 9th, 2010 @ 06:56 PM

    • Tag set to bugmash
  • Junihor Moran

    Junihor Moran May 15th, 2010 @ 07:40 PM

    • no changes were found...
  • Florent2

    Florent2 May 15th, 2010 @ 07:55 PM

    Steve, I am not sure I understand what you say.

    I could make work ":distinct => true" in a count like this (both in Rails 3beta2 and 2.3.5):

    Project.count(:name, :distinct => true)

    For scope, is it something like this you want?:

    scope :uniq_names, :select => :name, :distinct => true

    (You're right specifying :distinct in a scope does not work.)

  • Santiago Pastorino

    Santiago Pastorino February 2nd, 2011 @ 04:38 PM

    • State changed from “new” to “open”
    • Importance changed from “” to “”

    This issue has been automatically marked as stale because it has not been commented on for at least three months.

    The resources of the Rails core team are limited, and so we are asking for your help. If you can still reproduce this error on the 3-0-stable branch or on master, please reply with all of the information you have about it and add "[state:open]" to your comment. This will reopen the ticket for review. Likewise, if you feel that this is a very important feature for Rails to include, please reply with your explanation so we can consider it.

    Thank you for all your contributions, and we hope you will understand this step to focus our efforts where they are most helpful.

  • Santiago Pastorino

    Santiago Pastorino February 2nd, 2011 @ 04:38 PM

    • State changed from “open” to “stale”
  • Steve

    Steve February 2nd, 2011 @ 06:05 PM

    • Tag cleared.

    I think this ticket should probably be closed, it was started in 2009, the feature isn't a high priority and is now probably more related to Arel than rails anyway. [state: close]

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2 style="font-size: 14px">Tickets have moved to Github</h2>

The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>

People watching this ticket

Pages