5 ms·

TLDR: Definitely worth upgrading. Approximately hundreds of small bug fixes, across much of Rails. The fixes include some important ones for database types, t

by jph 10y ago

TLDR: Definitely worth upgrading. Approximately hundreds of small bug fixes, across much of Rails. The fixes include some important ones for database types, time comparisons, thread issues, record reloading, etc. IMHO these fixes address dozens of bugs that could cause major puzzlement for a typical Rails developer. Thanks to all the contributors for excellent work on this release.

avitzurel 10y ago
One of the best (or worst) bugs fixed was the aborted transaction for PGsql. I am pretty sure hundreds of Rails developers are battling it every day and don't understand where it's coming from. Even if you don't upgrade, this is something you should backport using a monkeypatch.
- seanp2k2 10y ago
  Do you have a link to the bug or the fix? We've seen this in prod for sure.
  - Exuma 10y ago
    Can you explain more what you saw? What fails, and how does it fail? Does it raise an exception and the transaction undoes all queries, or does a query 'half execute' and save a dirty state to the DB?
- faitswulff 10y ago
  I think that might be a 5.0.0 change, not a 5.0.1 change, if you're referring to: > Restore aborted transaction state when disable_referential_integrity fails due to missing permissions.
- Exuma 10y ago
  Do you have a link to that?
sfilargi 10y ago
> IMHO these fixes address dozens of bugs that could cause major puzzlement for a typical Rails developer. That has been the reason I always avoid huge frameworks like RoR. If I was to hit a bug like this, I wouldn't know where to start debugging. How do people deal with obscure bugs in the framework with something like RoR?
- Haydos585x2 10y ago
  They probably do it with all the spare time they have from using a framework to handle so many other features.
  - sfilargi 10y ago
    If you are lucky enough to hit it during development or testing, then yes, fair point. If you hit however in production and only under load or some corner cases, it must be a real bitch to try to debug code that you haven't wrote yourself. But since my original post is being seen as a troll, I think I will just shut-up and go hide under a rock or something. :D
    - reitanqild 10y ago
      Definitely not a troll I think. I guess downvoted because of disagreement. I'll also try to explain why: A few weeks later I have forgotten the specifics about my own code as well. Also: often there are fewer bugs in library code. And: getting help (paid or through stackoverflow) is probably easier.
      - sfilargi 10y ago
        > I guess downvoted because of disagreement. Fair enough :D > A few weeks later I have forgotten the specifics about my own code as well. > Also: often there are fewer bugs in library code. > And: getting help (paid or through stackoverflow) is probably easier. I can definitely see your point, especially about being easier to get help. I imagine if you are anything other than a one man shop, you will be in much better position debugging Rails or Django, rather than trying to figure out the mess you ex-employee left.
flukus 10y ago
> Approximately hundreds of small bug fixes, across much of Rails Bugs from 5.0.0 or from 4.whatever? If it's the latter then bug fixes should be going there, not in a new major release.
- sandstrom 10y ago
  This is 5.0.0 -> 5.0.1 (there is a separate branch for 4.x.y releases, but that's only security patches nowadays)

by jph 10y ago

avitzurel 10y ago

One of the best (or worst) bugs fixed was the aborted transaction for PGsql. I am pretty sure hundreds of Rails developers are battling it every day and don't understand where it's coming from. Even if you don't upgrade, this is something you should backport using a monkeypatch.

seanp2k2 10y ago
Do you have a link to the bug or the fix? We've seen this in prod for sure.
- Exuma 10y ago
  Can you explain more what you saw? What fails, and how does it fail? Does it raise an exception and the transaction undoes all queries, or does a query 'half execute' and save a dirty state to the DB?
faitswulff 10y ago
I think that might be a 5.0.0 change, not a 5.0.1 change, if you're referring to: > Restore aborted transaction state when disable_referential_integrity fails due to missing permissions.
Exuma 10y ago
Do you have a link to that?

sfilargi 10y ago

> IMHO these fixes address dozens of bugs that could cause major puzzlement for a typical Rails developer. That has been the reason I always avoid huge frameworks like RoR. If I was to hit a bug like this, I wouldn't know where to start debugging. How do people deal with obscure bugs in the framework with something like RoR?

Haydos585x2 10y ago
They probably do it with all the spare time they have from using a framework to handle so many other features.
- sfilargi 10y ago
  If you are lucky enough to hit it during development or testing, then yes, fair point. If you hit however in production and only under load or some corner cases, it must be a real bitch to try to debug code that you haven't wrote yourself. But since my original post is being seen as a troll, I think I will just shut-up and go hide under a rock or something. :D
  - reitanqild 10y ago
    Definitely not a troll I think. I guess downvoted because of disagreement. I'll also try to explain why: A few weeks later I have forgotten the specifics about my own code as well. Also: often there are fewer bugs in library code. And: getting help (paid or through stackoverflow) is probably easier.
    - sfilargi 10y ago
      > I guess downvoted because of disagreement. Fair enough :D > A few weeks later I have forgotten the specifics about my own code as well. > Also: often there are fewer bugs in library code. > And: getting help (paid or through stackoverflow) is probably easier. I can definitely see your point, especially about being easier to get help. I imagine if you are anything other than a one man shop, you will be in much better position debugging Rails or Django, rather than trying to figure out the mess you ex-employee left.

flukus 10y ago

> Approximately hundreds of small bug fixes, across much of Rails Bugs from 5.0.0 or from 4.whatever? If it's the latter then bug fixes should be going there, not in a new major release.

sandstrom 10y ago
This is 5.0.0 -> 5.0.1 (there is a separate branch for 4.x.y releases, but that's only security patches nowadays)