I agree with Matt on this subject. Even if we could come up with useful
heuristics, we would not deprecate includes, eager_load and preload. There
are always situations you can't detect. Also I wouldn't want to use that
feature on some of my apps. It can be crucial what Query is executed and
su
On May 16, 2014, at 2:35 PM, Lawrence Wu wrote:
> I'd like to deprecate methods like includes and eager_load in Rails since I
> think it is possible to automatically detect when they are needed. Ideally
> the developer could know very little about how databases work and still get
> very effic
I’ve had to resort to some pretty weird cookie stuff when passing data between
a Rails app and non-Rails applications. The session is handy, but parsing it
anywhere but in Rails is difficult and *updating* it outside of Rails is more
difficult.
—Matt Jones
On May 17, 2014, at 9:12 AM, Gabriel
I don't think you can use Rails sessions without cookies support...
Em 17/05/2014 10:12, "Gabriel Sobrinho"
escreveu:
> I would argue that if you have some information that can't be hijacked and
> even parsed on javascript (httponly cookies can't be read on javascript at
> all), why would you use