Project

General

Custom queries

Profile

Actions

Refactor #3540

open

Change pluck('table.column') back to pluck(:column)

Added by Dominic Cleal over 11 years ago. Updated over 9 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Rails
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

For Rails 3.2.8 compatibility, we've changed a few instance of pluck(:column) to specify the table name to remove ambiguity (which 3.2.13 and higher can cope with). These can be reverted on Rails 4 or similar.


Related issues 1 (0 open1 closed)

Related to Foreman - Tracker #3157: Rails 4.1 upgrade tasksClosed09/27/2013

Actions
Actions #2

Updated by Dominic Cleal over 11 years ago

b1e56e3c62535fd89ed4e226c56961cb5e8a3e3e #3538
65f764d6081b04cd03fa56a78e6281b5221b0bac #2579

Actions #4

Updated by Dominic Cleal over 11 years ago

  • Subject changed from Change pluck('table.column') back to pluck('column') to Change pluck('table.column') back to pluck(:column')
  • Description updated (diff)

Oops, thanks Petr. The string was laziness, I hadn't realised it was different!

Actions #8

Updated by Tom Caspy about 10 years ago

I'm not sure I want this.
specifying the table name in situations where there's a join makes a lot of sense to me. it's more verbose, and feels right to me. let's keep it like it is.

Actions

Also available in: Atom PDF