> On Mar 16, 2016, at 3:03 PM, Jeremy McNevin wrote:
>
> I'd be interested in hearing thoughts about changing the generated SQL for a
> negated equality comparison from using "!=" to "IS DISTINCT FROM" (where
> supported), since the latter has less-surprising handling of
A small set of Rails features are dependent on the inclusion of jQuery.
Basically, it's everything UJS does. Including all of jQuery to support UJS
feels like a heavy weight solution. In the past almost everyone was using
jQuery so it seemed reasonable to include. The explosion of JS in the
Yeah, we definitely could never make this change. It'd be too major of a
backwards incompatible change.
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
I'd be interested in hearing thoughts about changing the generated SQL for
a negated equality comparison from using "!=" to "IS DISTINCT FROM" (where
supported), since the latter has less-surprising handling of NULL values.
For example, with the following bit of AR:
User.where.not(parent_id:
Hi Aaron,
That is one of the goals of this year's GSoC:
https://github.com/railsgsoc/ideas/wiki/2016-Ideas#implement-ujs-using-native-javascript
--
Roque Pinel
On Thu, Mar 17, 2016 at 1:38 AM, Aaron Lasseigne
wrote:
> A small set of Rails features are dependent on